review

# Review Review and report only. Do not modify code, commit, push, merge, resolve review threads, or post GitHub comments unless the user explicitly asks for posting. ## 1. Establish the review target Prefer, in order: 1. The PR base and head named by the user or `.codex-review-context.json`. 2. The current branch's PR from `gh pr view`. 3. Uncommitted and staged changes. 4. `origin/main...HEAD` for a committed branch. Fetch only a missing base ref. If the diff is empty, stop. Record the exact base and head SHAs so a later force-push cannot silently change the target. For CI reviews that provide trusted base/head refs in `.codex-review-context.json`, use those refs directly. Keep the trusted base checked out and inspect contributor files with `git diff` and `git show <head-ref>:<path>`; do not materialize or execute the contributor tree. For a merge-ref checkout supplied by another trusted harness, review the parents and do not attribute the synthetic merge commit to the contributor. ## 2. Build one evidence packet Gather once and share with every reviewer: - PR description and linked issue, commit list, changed paths, and diff. - Post-change bodies of touched functions. A hunk alone is not enough. - Root `AGENTS.md` and relevant system-of-record docs: `ARCHITECTURE.md`, `trust-model.md`, `code-style.md`, `testing.md`, `.cargo/mutants.toml`, command/config references, and nearby platform notes. - Prior review bodies, PR comments, and inline threads. Treat them as...