triage
Triage
Move issues through a small state machine on the repo's configured tracker. Read the tracker operations from docs/agents/issue-tracker.md and the label strings from docs/agents/triage-labels.md; if either is missing, say so and suggest configure-repo before continuing (you can still triage read-only in the meantime).
If the tracker config says external pull requests are a request surface, they go through the same machine — a PR is an issue with attached code. Collaborators' in-flight PRs are not triage work; an explicitly named PR is always in scope.
Every comment you post to the tracker starts with this exact line:
> *This was generated by AI during triage.*
Supporting reference: agent-brief-template.md — the brief format and its durability rules.
The state machine
Two axes; every triaged issue carries exactly one label from each: