Route incoming issues so external contributors get a useful response and maintainers can see what needs their attention. Adapt the gh-aw [Issue Triage gallery pattern](https://github.github.com/gh-aw/gallery/ai-issue-triage/) with four routes: agent candidate, human response, needs information, and internal backlog note.

- Acknowledge external reports with one short automated comment; label internal notes quietly. Agent candidates remain recommendations requiring human authorization. - Run on new/reopened/edited issues and human replies, on merge of this workflow, daily at 09:43 UTC, or manually. Catch-up handles five issues at a time, oldest external reports first; unchanged reports skip inference. - Use Codex with GPT-6.1 Sol at low effort and the existing API key. Shell, web search, and external fetch are disabled; repository reads stay scoped to Chopin. No contributor checkout, code changes, agent assignment, closure, or workflow dispatch. - Cap public-user triggers at three per hour and AI usage at 100 credits per run / 500 daily. `no-triage` opts an issue out. Routing and opt-out labels have already been created.

### Routing and contributor replies


### Validation

- Seven selector tests pass (22 assertions): backlog priority, pagination, exclusions, deduplication, forged markers, human updates, and quiet internal notes. - `bun run ci` and `bun run types` pass; seven existing lint warnings. - Strict gh-aw compilation and schema validation pass. Generated shell scripts parse; selection dependencies, no-op guard, disabled agent shell, and model configuration inspected. - Read-only live selection picks #149, #150, #151, #154, and #203. No comments have been posted and no issues have been relabeled yet. - Model triage and write application await merge; replies are AI judgments and need initial human review.

<details><summary>Compiler and credential review</summary>

Compiled with gh-aw v0.86.2. Reviewed the new workflow references to existing `CODEX_API_KEY` and the engine's `OPENAI_API_KEY` fallback: model credentials are held by the framework proxy. No maintenance PAT is used. The selected metadata injected into the prompt contains only issue numbers, internal/external classification, timestamps, and receipt markers, with issue prose read as untrusted data through read-only GitHub tools.

New workflow action references are compiler-pinned gh-aw setup, github-script, artifact actions, and the trusted main checkout. Selection runs trusted repository code with a read-only token. Threat detection is fail-closed and uses a separate Codex engine to avoid inheritance of the compiler's malformed detection argument concatenation.

This compiler lacks the issue-only option for `remove-labels`, so its shared label-removal and conclusion jobs request `pull-requests: write` alongside `issues: write`. Safe outputs restrict additions to nine named labels, removals to the four routing labels, and comments to five per run; there is no content-write, PR creation, push, merge, assignment, or dispatch output. The workflow prompt limits all actions to selected open issues. The rate-limit feature is marked experimental by gh-aw; daily budget and five-issue selection limits are also configured.

</details>