swarm-implementlisted

# swarm-implement — implementation phase Two roles. Check flow-state: no tickets yet → you're the **planner**; tickets exist → you're a **worker**. ## Planner (strong model, once per milestone batch) **Gate:** validated design. Read `docs/design.md` and the milestone's FR specs. 1. Emit tickets to `30 Plans/<P>/tickets/TK-NNN-<slug>.md` (template: `90 Templates/ticket.md`, machine lane): FR-ID trace, `requires:` edges (tracer-bullet order: thinnest end-to-end slice first), suggested `tier` (size) and `kind` (`design`/`planning`/`coding`/`review`/`docs` — lets orchestration route the right model), DoD checklist, and CONTEXT — the exact notes/design sections a worker needs (nothing more). 2. Ask the user ONCE (skip in auto mode if already answered at SRS validation): parallelism appetite, and is a browser/test environment available for UI verification? 3. Update flow-state (`phase: implement`, ticket count) — J1: state first, work second. **Model tiers:** `top` — architecture-touching, complex logic, tricky concurrency; `mid` — standard features, refactors; `small` — boilerplate, docs, simple UI. Workers on the wrong tier for a ticket should say so rather than proceed on hard tickets. ## Worker loop (any agent, any platform, N in parallel) 1. **Pick:** next `status: open` ticket whose `requires:` are all `done` (`swarmvault.py query --project P --type ticket`). If orchestration is on, check `board --project P` first: a ticket listed **for this sessio