roundnext

# /roundnext — one planned/blocked/new-work round Mechanizes the composition of Constellation §13.16.6 element 5 (planned-queue scan), §13.20 (blocker tracking + nudge), and §13.18 (autonomous execution) into a single invocable round. The output of a round is: work started, queues re-sorted, blockers acted on, new work registered, and human-gated items routed to the decisions panel — never a silent "nothing to do". ## Procedure (5 steps, in order) **0. Load board truth** — read the live board state (`board_state_get` MCP tool, or the board's `state.json` directly). You need: `planned[]` (with `blocked`/`blockReason`/`when`), `current`, `decisions[]` (open ones), and recent `done[]` for context. **1. Ripeness check on unblocked planned items** — for each planned item that is not blocked, ask: has its start condition arrived? (`when` reached, predecessor in `done[]`, ordering satisfied, no fresher priority above it.) If ripe → **start it now** (§13.18: a defined-next-step proceeds without asking). When the started item is a multi-stage track (3+ phases, or spanning sessions/external waits), register it on `current[]` **with a `stages` timeline** (§13.31.4 — `{label, status: 'pending'|'active'|'done'}`); this start step is the schema's natural entry hook. If not ripe, record why in one line (this becomes the priority rationale in step 2's sort). **2. Blocker re-examination on blocked planned items** — for each `blocked: true` item, re-verify the blocker *now* (don't trust t...