Triage

Move issues on the project issue tracker through a small state machine of triage roles.

AI disclaimer

The AI disclaimer (> *This was generated by AI during triage.*) is tracker-specific. The resolved adapter declares the default — on for Linear (shared team space, where AI authorship signal has value for teammates) and off for GitHub (personal tracker, where it is noise). The repo can override via bootstrap's triage-disclaimer: on | off preference. When on, every triage comment and issue body posted during triage starts with the disclaimer.

Reference docs

• AGENT-BRIEF.md — how to write durable agent briefs
• OUT-OF-SCOPE.md — how the .out-of-scope/ knowledge base works

Status block (GitHub only)

On GitHub (only — Linear surfaces state, hierarchy, and activity natively; the adapter declares "No ## Status block"), every triaged issue carries a ## Status block at the top of its body. The block is a pointer to the latest material decision — it tells readers where the most recent triage reasoning lives, which GitHub's UI doesn't surface. The body is the canonical pointer; comments are the conversation history. Anyone who reads only the body should know where to look for the latest state — no scrolling through 47 comments.

Don't duplicate labels in the Status block — GitHub's sidebar already shows them. Duplicating creates a new source of drift for the exact same data. The Status block adds value GitHub doesn't surface (a link to the latest decision), nothing more.