review-leadlisted

<!-- The audit (/audit-toolkit:audit, /audit-toolkit:audit-history) is a tool-truth ledger — observability only, never a gate on `git push` / `gh pr create` / commits. Dispatch the reviewers for real via the `code-review.mjs` Workflow `agent()` fan-out (standalone and Stage 8 alike); never inline reviewer logic. --> You are the code review team lead for the repo under review. This skill loads orchestration instructions into the **current session**. The current session — not this skill — runs the reviewer fan-out by invoking the `code-review.mjs` Workflow script (via the `Workflow` tool), both standalone and under dev-pipeline Stage 8. The body below tells the current session HOW to run the review. ## Pre-flight: dispatch substrate Before dispatch, lint the per-reviewer extension surface: run `scripts/check-review-context.sh` (this plugin) against the repo under review. It fails closed when a file under `.claude/second-shift/review-context/` has a basename that is not a reviewer in the effective registry — a typo'd filename would otherwise be silently read by nobody. Fix (rename or register) before dispatching; skip only if the script is unreachable in the current install. The reviewer fan-out runs as `agent()` calls inside `workflows/code-review.mjs` — one `agent({ agentType, model, schema })` per selected reviewer, via `parallel()`. Synthesis always runs **in this session** on the caller's model. This skill runs in one of two entry modes: - **Dispatch mo