Triage

Move tasks on the configured tracker through a small state machine of intake roles. Triage acts on remote records or local intake task bodies; unresolved proposals in a capability's draft have no role.

If the tracker treats external pull requests as a request surface, triage covers them too. A PR is a task with attached code, using the same roles and states, with the differences noted below. Resolve a bare #42 to an issue or PR through the tracker configuration.

Document and tracker contract

The project documents and their rules are in project-documents.md; read it before updating project documents. Its terms (authorized, obligation, lazy, pointer) apply throughout. Read the relevant requirements, specifications, working state, and backlog when present.

Read the task tracker configuration and the triage roles that AGENTS.md points to. When the tracker configuration is missing, ask the user where the tasks live for this run (the repository remote's issue tracker through its command-line tool or a connected server, or local intake task bodies) and verify read access with one read-only query before triaging. When the roles are missing, use the canonical strings below. Say in the report which configuration was missing and what this run assumed; record nothing as configuration.

"Comment", "apply a role", and "close" resolve through the tracker configuration:

• Remote operations use the platform's actual commands and labels. A local title/link reference to a published remote task does not duplicate remote role state.
• Local task bodies use Category: and Status: near the top. Comments append under ## Comments. Rejection closes intake with Status: not-planned. Delivery progress, blockers, and acceptance evidence can be recorded in the body separately from intake state.

Remote comments, role changes, and closing need authorization from the maintainer's explicit triage request or confirmed outcome. A generic local document edit grants no remote publication authority. Maintain specifications, active work, and the changelog locally within scope. Candidate deferrals follow the backlog authority in project-documents.md; do not create a local queue beside a remote backlog.