REVIEW BRIEF — REV: FINAL: REVIEW ACCEPTANCE: scripts/check-scope FOCUS: SEVERITY SCALE: P0 blocks the step; P1 is serious; P2 is minor. QUESTIONS TO ATTACK: <> An item is a question, not a prediction: word mutant items as "which pin goes red, and on which member?" — the reviewer measures it. A mutant prediction names the first member the runner reaches. --- BEGIN BRIEF UNDER REVIEW (copy of ; the committed file is authoritative) --- <> --- END BRIEF UNDER REVIEW --- You did not write this code and you will not fix it; a finding is output, not an action. The step's decision is the planner's (cycle step 5): report findings, never decisions. The commits under review carry the trailer `Actor: IMPLEMENTER`; if your session wrote any of them, stop and say so. Run REVIEW ACCEPTANCE first: it is the method's only gated check. The ACCEPTANCE lines inside the brief under review are the implementer's; re-run them to verify the delivery, and run `scripts/check-tests` as your standing battery — the full suite is your falsification ground — recording both in `VERIFIED`. Every pytest line names .venv/bin/python -m pytest (bare pytest lacks pytest-timeout; strict config rejects it), and every suite run prints its slowest five (--durations=5) so budgets are set from measured per-test walls. A gate command that constructs sandboxes runs under `systemd-run --user --scope` where the session's own scope is not cgroup-delegated — a bare session fails `cgroup placement failed: Errno 13`, while the scope inherits your environment's PATH. The embedded brief is a convenience copy: if the standalone file it names differs, file a FINDING with ORIGIN: BRIEF and review against the committed file. You may create new test files to prove a finding, and modify nothing else. If a failing test would need registering in tests/open_defects.yaml, say so in the report and leave the registration to the next implementer brief rather than editing that file; the registry owns test_bug_* pins only, and a test_review_* probe rides red until absorbed. Read pre-images with git show :..., not the implementation's account of them. Run every mutant on a scratch copy of the tree, and diff each mutant against git show :... before trusting its result. Attempt to falsify the brief, not only the code: a finding that the brief was wrong is a finding, and so is a defect the implementer filed only as friction. Answer every item under QUESTIONS TO ATTACK. Keep every line an agent must read under 2,000 characters — the session reader truncates longer lines with its own marker, and a wrapped line is readable where a clipped one is archaeology. Answers live in the form's fields — a finding in FINDINGS, a measurement in VERIFIED/SHAPES. An added review's QUESTIONS TO ATTACK come only from the implementer's report — never from another review's findings. Enumerate the shapes you probed that the existing suite does not build, as a list; zero with a stated reason is legitimate. Report each guarantee as falsified-with-reproducer or attacked-and-not-falsified with the method. Commit your own work: your new test files and your report, together, in one commit whose message ends with the trailer `Actor: REVIEWER`. Append docs/templates/report.txt verbatim, fill it in, and write it to docs/research/--review.md. If you cannot commit, stop and say so.