Repo Maintainer

Make cross-repository consequences visible before accepting, implementing, or declaring a change complete. Scale review and verification to semantic risk, not diff size alone.

Select the operation

• Assess an incoming change: inspect it read-only and recommend adopt, adapt, defer, or reject. Do not pull, merge, cherry-pick, or edit merely because assessment was requested.
• Implement maintenance: map impact, make the smallest complete change, and verify the resulting diff.
• Audit existing work: review every changed hunk, find omissions and regressions, and report findings before editing unless the user also asked for fixes.
• Prepare a release: inspect the complete release delta and read references/verification.md plus any repository release instructions.

Read repository instructions before acting. In this repository, also read references/codex-router-surfaces.md when a change touches routing, providers, clients, installers, credentials, the gateway, model publication, desktop surfaces, or releases.

Establish the evidence baseline

1. Preserve unrelated work. Inspect status, current branch or detached state, relevant instructions, and the requested comparison boundary.
2. Run the analyzer from the repository root. The command below is read-only; adding --manifest PATH atomically creates or replaces that named JSON artifact: