AFK Pipeline

Substantial eligible development routed to AFK uses a GitHub-issue label to trigger a pipeline that implements the change, verifies it in a real browser, opens a draft PR carrying committed QA Evidence, and — only when the requester asked for one — publishes a visual recap. A human reviews and merges. In a registered repo on the AFK lane you never implement product code inline — your deliverable is the brief, and the brief is the contract: the pipeline agents get no follow-up questions.

Preamble (run FIRST)

cd "$(git rev-parse --show-toplevel)" 2>/dev/null
_R=.agents/afk-pipeline/REGISTRY.md
[ -f "$_R" ] && echo "REGISTRY: $_R" || echo "REGISTRY: missing"

• REGISTRY: missing → either you are not in the consumer's home repo (ask where the registry lives), or the pipeline was never adopted here (offer reference/installation.md).
• Otherwise Read the registry file in full now — it maps each repo to trigger labels, default lane, clone path, and quirks. Do not route from memory of it.

Contract