wave-drainlisted

# Wave Drain **Goal:** Drain the open backlog at maximum throughput. Every workable issue ends either **merged** (inside a wave PR merged GREEN) or **needs-human** with a blocker report. **Mental model:** You are the Claude Code **orchestrator**. You do **not** implement — you **direct parallel agents**. Tokens are saved by running the heavy ceremony **once per wave** (one cumulative plan, one plan review, one code review, one full gate, one PR), never by skipping phases. > `/ship` drives **one issue → one PR**. Wave Drain is its multi-issue sibling: **N issues → > one wave PR**, reusing the same engine and the same gates. **Legality (ADR-103):** parallel write-agents are in-contract ONLY under the rule-50 carve-out — every agent in a **dedicated worktree** (`/wt-open`), on a **distinct branch**, with **plan-manifest-disjoint file-sets**. Dependency changes (`package.json`/lockfiles), main-tree edits and tags stay serial-only. **Convergence model (owner-ratified 2026-07-10):** on arbiter-governed repos every wave converges into **ONE wave PR** — the parallelism is in HOW the wave is built, never in N PRs racing to `main`. For repos WITHOUT arbiter governance, see the **cross-repo appendix** at the end (N-PR + merge-train). ## Primitives | Primitive | Role here | | ---------------------------------------------------------- | -------