Implement AFK Agentic

Implement one ticket with nobody at the keyboard. The ticket is the human input for the run: execute what it settles and halt on what it leaves open.

When configuring this workflow in a new repository or changing its lifecycle, read references/afk-implementation.md.

Preconditions

Before writing code, read the issue tracker, triage-label, domain-doc, and repository instructions. Confirm that:

• the ticket carries the configured ready-for-agent label;
• the ticket has a filled Seams under test section;
• its acceptance criteria are testable and unambiguous;
• the repository declares its PR target/integration branch, or its remote default branch can be resolved unambiguously; and
• the issue tracker operations needed to comment and relabel are available.

Any failed precondition triggers the halt rule. A ticket without named seams was never AFK-ready.

Branch