triage

原文涵盖的主题

• Triage
• Reference docs
• Roles
• Invocation
• Show what needs attention
• Triage a specific issue or PR
• Quick state override
• Needs-info template

Move issues on the project issue tracker through a small state machine of triage roles. If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: a PR is an issue with attached code, using the same roles, same states, and same machine, with a few deltas marked "for a PR" below. Resolve a bare #42 to an issue or PR per the tracker config. Every comment or issue posted to the issue tracker during triage must start with this disclaimer: AGENT-BRIEF.md: how to write durable agent briefs OUT-OF-SCOPE.md: how the .out-of-scope/ knowledge base works Two category roles: bug: something is broken enhancement: new feature or improvement Five state roles: needs-triage: maintainer needs to evaluate needs-info: waiting on reporter for more information ready-for-agent: fully specified, ready for an AFK agent ready-for-human: needs human implementation wontfix: will not be actioned For a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge. Every triaged issue should carry exactly one categor

这里只展示节选，请以完整原文和当前要求为准。