spae-spawnlisted

# Spawn ## When to use - The user wants to perform the build phase of the `SPAE` structured workflow autonomously. ## Goal - Spawn the subagent matching the current `STATE.json` phase, looped until every task completes. - Ensure `phase: verify` in `STATE.json` once the loop exits. ## Input Read `.spae/current/STATE.json` for phase, cursor, and task registry. ## `STATE.json` See `references/STATE.md` for the field reference, directives, and phase snapshots. ## Phase-agent map Every phase maps to exactly one subagent, spawned the same way regardless of phase: | `phase` | Subagent | | ------- | -------- | | `build` | `build` | | `check` | `check` | | `fix` | `fix` | ## Workflow 1. **Validate State**: Confirm `STATE.json` has `phase` in `"build"`, `"check"`, `"fix"` and a populated `cursor.active_task_id`. Halt on malformed or missing `STATE.json`, or an unrecognized `phase`. 2. **Dispatch Loop**: - Re-read `.spae/current/STATE.json`; record `phase`. - Exit on `phase: "verify"`. - Halt immediately if `phase` matches none of the phase-agent map's rows. - Spawn the subagent the map names for the recorded `phase`, no arguments. - Await completion; halt immediately on `Failed` status or any process failure (crash, timeout, `AgentError`). - Re-read `.spae/current/STATE.json`; halt immediately if `phase` matches the value recorded at the start of this iteration. - Repeat step 2. 3. **Finalize Phase**: Confirm `STATE