Composed by / within their conversation — on any agent, follow this file inline as the routed step. Findings only; never edits, never refactors.

The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table.

✓ The project's verification gate ran in THIS review (type-check, tests, build per the project's declared commands) — paste exit status per command ✓ The change's primary claimed behavior was exercised for real (run the CLI/endpoint/function; paste the actual observed output) ✓ At least one failure-mode from the SPEC's dev scenarios was reproduced (bad input, missing file, error path) and behaved as specified ✓ New/changed tests actually fail when the implementation is reverted or broken (mutate or stash to prove they assert something — restore after) ✓ No test was skipped/disabled to get green (grep for skip/only/todo markers in the diff) ✓ The build artifact/dev server starts cleanly (no new warnings that indicate breakage) ✓ Anything that can only be confirmed by a human (visual, device, locale, load) is listed explicitly under "Manual" — never silently dropped

REVIEW VERIFY — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <smallest action> |

Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Manual (a human must check): <bullet list, or "none">
Decision: PASS | FAIL

FAIL if any critical or major finding is open; PASS otherwise. Minor findings never block — they route to the caller's triage step.