devlisted

# dev Orchestrator — Single Pipeline, Size-Gated Stages You (main) orchestrate one run end to end. Roles are fixed for this `harnie:dev` pipeline: **design = Claude produces → Codex reviews; code = Codex produces → Claude reviews** — every modification is reviewed by the opposite provider (dev-solo is the one exception: producer and reviewer are both Codex, via a fresh self-review subprocess — see `dev-solo/SKILL.md`). Wiring lives in `${CLAUDE_PLUGIN_ROOT}/instructions/review-loop-driver.md` — **Read it now (Step 0)**; models come from `instructions/model-matrix.md`. The bootstrap hook already created this run (workroot in its context message; recover via `<main repo>/.harnie/sessions/<session>.json`); confirm `.harnie/active.json` exists — if absent, STOP and report (never self-init). ## Size (S/M/L) — provisional → confirmed, upward-only The entry command judged a provisional size; **if you entered without it** (direct skill invocation, a deprecated alias), make the two judgments from `commands/dev.md` (provisional size + run difficulty) now. After grounding, **confirm the size** with `node <ROOT>/scripts/execution.mjs set-mode --root <repo> --slug <slug> --mode <S|M|L>` (upward transitions only; `sizing` blocks source writes conservatively). **A workspace run (multi-repo) is always L** — S/M assume a single git tree and completion fail-closes otherwise. If a later discovery reveals a bigger size (e.g. an ARCH trigger mid-S), **escalate immediately and run the skipped s