cursor-implementlisted

# Implement via `cursor-agent` A paid-pool write leg whose family is **whatever model you pin** — a cursor-served Codex tier produces GPT-family work, a cursor-served Sonnet produces Claude-family work. The cross-family rule reads the served model's family: the reviewer for this leg's output must come from a different family than the one you pinned here, and `auto`/`composer-*` output (family unknown/undisclosed) must be reviewed by TWO named families to be safe — cheaper to just pin a named model when the work will need a gate. ## Before the first run of a session Read **[`references/cursor-runtime.md`](../cursor-adversarial-review/references/cursor-runtime.md)**. What bites the write role: bare `-p` already has full write and shell access (measured — no `--force` needed, and none of `--force`/`--yolo`/ `--approve-mcps` may appear anyway), the prompt rides argv with an unverified size cliff, and quota exhaustion is loud (`ActionRequiredError`, exit 1) so a dead dispatch tells you immediately. ## Worktree, snapshot, then dispatch Every write leg gets its own worktree, without exception — same rule, same helpers, same reasons as the other families (the CLI's own `--worktree` under `~/.cursor/worktrees` is not used; the suite's helpers own directory lifecycle): ```bash RUN_DIR=$(mktemp -d "${TMPDIR:-/tmp}/cursor-implement.XXXXXX") # FIRST — the snapshot lands here BASE=$(git rev-parse HEAD) # from a clean checkout, recorded before anything WORKTREE=../<repo>-cursor-<s