spae-checklisted

# Check (`SPAE`) ## When to use - `STATE.json` reports `phase: check`. - Cursor names active task. ## Goal - Compare active task implementation against PLAN.md Intent, Acceptance, and Verification. - Route gaps to /fix or advance clear task. ## Input Read: - `.spae/current/STATE.json` (consult `references/STATE.md` for field reference, directives, and phase snapshots) - Active task section from `.spae/current/PLAN.md` (`Intent`, `Acceptance`, `Verification`) - Source files and test logs scoped to active task ## Workflow 1. **GATE**—Read `.spae/current/STATE.json`; confirm `phase: check` and `active_task_id`. Self-heal state drift: if `tasks[`active_task_id`]` reads `"todo"`, correct it to `"in_progress"` and write `STATE.json` before proceeding. Halt on state drift: if `tasks[`active_task_id`]` reads `"done"`, halt. Read active `PLAN.md` task section; confirm title, `Intent`, `Acceptance`, `Verification`. Halt on missing or malformed input; report and make no changes. 2. **ORIENT**—Verify active task; hand off to `/fix`, `/build`, or `/verify`. Leave source, tests, `config`, docs, `PLAN.md`, `SPEC.md`, task scope, and `workstream` completion untouched. 3. **PLAN**—List active-task `Acceptance` outcomes and `Verification` steps. Map evidence for declared `Intent`; scope source/test reads to active task. Never read `SPEC.md`. 4. **ACT**—Execute: - Run active-task verification steps and project checks. Without automation, insp