review-fix-prlisted

# review-fix-pr Reviews a PR diff: the file set changed between `base=<branch>` and `HEAD`. This is a code route, not a document route. It has no document type and no reference documents. Users must not pass `target=`, `type`, `ref=`, `assurance=`, `strict`, `normal`, or `ledger=`. Invocation syntax: ```text review-fix-pr base=<branch> [read-only|review-and-fix] [guard=git|snapshot] [resume|reset] [rounds=<n>] [root=<project-root>] [debug] ``` `base=<branch>` is required and names the merge base for the diff; `HEAD` is the other end. There is no bare-path or `target=` form. Valid invocations may omit mode. On Codex and Claude Code, missing mode selects `review-and-fix`. This code route exposes no user-facing `assurance=` token; for `review-and-fix` it internally materializes `practical` assurance (or `strict-verified` only on the same-flow strict proof path), so code auto-fix is never rejected as `advisory-review-and-fix-unsupported`. Gemini generated routes are advisory-only and render `review-and-fix` as unsupported; they produce read-only findings only and must not claim workflow PASS. Help-style or invalid invocations explain usage only and do not read files, run workflow commands, run probes, create state, or declare review results. Code review is actionable-only: pure style preferences, no-risk refactors, and over-abstraction are not blocking. Judge the changed file set for correctness, regressions, safety, tests, contracts, and maintainability. `rounds=<n>` set