review-looplisted

# review-loop — bounded delta review with receipts Read `delivery-methodology` and repo instructions first. Review is a risk-control tool, not a stochastic search for a panel that eventually says nothing. ## Required target Do not start from “review this branch.” Name: - artifact type and scope; - `base_sha` and `head_sha` (or exact plan revision); - acceptance criteria and important invariants; - risk tier and requested lenses; - focused checks/evidence already available. Treat the declared subject, acceptance criteria, invariants, and `base_sha..head_sha` as a hard scope lock. Read only the surrounding context needed to validate impact; untouched context is evidence, not a new audit surface. A finding is in scope only if the target delta introduced or changed it, or the delta makes an existing path violate an explicit acceptance criterion/invariant. An explicit plan review may use plan revisions instead of Git SHAs. ## Risk-scale the panel - **Routine:** one reviewer. - **Sensitive:** two independent reviewers/lenses for authorization, migrations/storage, protocol/compatibility, concurrency, native code, destructive behavior, or credible data-loss risk. - **Exceptional:** three only for exceptional blast radius. Reviewers report concrete failure paths, violated requirements/invariants, and evidence. Exclude style nits, speculative refactors, unrelated pre-existing debt, unsupported hypotheticals, and issues a required compiler/linter already settles unless they