cursor-adversarial-reviewlisted

# Adversarial review via `cursor-agent` (ask mode) The value of this leg is **family width through one adapter**: pin the model per round and the same CLI can be a GPT, Claude, Grok, or Kimi reviewer — whichever family the cross-family accounting still allows. The model flag IS the accounting decision; `auto` and `composer-*` never satisfy the rule (runtime file, accounting rules). ## Before the first run of a session Read **[`references/cursor-runtime.md`](references/cursor-runtime.md)** (same directory). The three measured postures matter more than anything else in it: bare `-p` writes files without asking, `--mode plan` headless returns empty output every time, and `--mode ask` is the one posture that both refuses writes and delivers a report. The skill below assumes those three facts; do not re-derive them at dispatch time. ## Establish an immutable review target **One frozen directory per reviewer, at the exact commit, that nothing else touches — no lead activity inside it.** Not "whenever possible": a reviewer reads the WORKING TREE, not your commit. Measured — a round ran mutation testing in the same worktree mid-review and the reviewer opened a CRITICAL on a mutated, non-compiling file it was never meant to see. Freeze it with the suite's tested helpers instead of hand-rolling the shell; every bug ever found in this step was in a hand-rolled copy. The suite-root resolver and both calls — `freeze-target.sh` to create it, `verify-target.sh` before AND after the ru