github-triage

State-machine triage over GitHub issues. Every comment posted carries an AI disclaimer. Label names are configurable; state semantics are not. ## AI disclaimer (mandatory) Every comment or new issue body posted during triage MUST begin with: ``` > *This was generated by AI during triage.* ``` No exceptions. ## Label map (configure per project) Bind ODIN's abstract state tokens to your repo's actual label names. Edit this block before first use; defaults match Matt Pocock's upstream convention. ``` category: bug: "bug" # something is broken enhancement:"enhancement" # new feature or improvement state: triage_pending: "needs-triage" # maintainer must evaluate awaiting_info: "needs-info" # waiting on reporter ready_for_agent: "ready-for-agent" # fully specified, autonomous-agent-suitable ready_for_human: "ready-for-human" # requires human judgment wont_fix: "wontfix" # closed, not actioned ``` Body uses the abstract tokens (`triage_pending`, `ready_for_agent`, etc.). Replace with your repo's labels at apply time. ## Invariants - Every issue carries exactly one `category` label and one `state` label. - Conflicting state labels = halt and ask the maintainer which is correct. - Maintainer can override any state directly; flag unusual transitions. ## State machine | From | To | Trigger | Effect | ...