spae-verifylisted

# Verify `SPAE` ## When to use - `STATE.json` reports `phase: verify`. - Every `PLAN.md` task reports `done`. ## Goal - Compare implemented repository state against `SPEC.md`, identify gaps, and close or reopen the work stream as the final `SPAE` arbiter. - Pass: complete the work stream. - No pass: route actionable gaps back to `/spec`. ## Input Read: - `.spae/current/STATE.json` (consult `references/STATE.md` for field reference, directives, and phase snapshots) - `.spae/current/SPEC.md` - `.spae/current/PLAN.md` - All source files modified by this **workstream** (scoped from `.spae/current/PLAN.md` tasks) - `.spae/current/VERIFY.md`, when present ## Workflow 1. **GATE**—Read `.spae/current/STATE.json`; confirm `phase: verify`. Confirm every `.spae/current/PLAN.md` task reports `done` in the `tasks` registry. Halt immediately on failure; report which check failed; make no changes. 2. **ORIENT**—Goal: compare implemented repository state against each `.spae/current/SPEC.md` spec item; determine pass, no-pass, or blocked verdict. 3. **PLAN**—List `SPEC.md` spec item IDs and source files modified by this `workstream` (scoped from `PLAN.md` tasks). 4. **ACT**—Execute: - Run all relevant project checks. When no automated checks exist, inspect observable behavior directly—reading code and logs or running scripted probes—never delegating execution or evidence capture to a human, an attended terminal, or an interactive session