spae-inspectlisted

# Inspect (`SPAE`) ## When to use - `STATE.json` has `phase: inspect`. - `PLAN.md` needs validation against `SPEC.md`, codebase patterns, or technical constraints before execution. ## Goal - Tighten the atomic task graph before execution while keeping the repository source read-only. - Find gaps between `SPEC.md`, `PLAN.md`, and relevant codebase context. - Fix each classified gap fully; match correction depth to finding severity, not diff size. - Advance the `workstream` to execution readiness. ## Input Read only what the inspection requires: - `.spae/current/SPEC.md` - `.spae/current/PLAN.md` - `.spae/current/STATE.json` (consult `references/STATE.md` for field reference, directives, and phase snapshots) - Relevant source files for context only. **Never read `.spae/current/VERIFY.md`**—not an input to this phase. Reading qualifies as content-blocking. ## Workflow 1. **GATE**—Read `.spae/current/STATE.json`, `.spae/current/SPEC.md`, and `.spae/current/PLAN.md`. Halt when `phase ≠ inspect`. 2. **ORIENT**—Goal: tighten the task graph for execution readiness. Source stays read-only; `SPEC.md` unchanged. 3. **PLAN**—Classify each gap before editing `PLAN.md`. Declare the minimal refinements the findings demand. 4. **ACT**—Apply classified findings only. Compare requirements, plan tasks, acceptance criteria, verification steps, dependencies, and codebase patterns. - Flag any `SPEC.md` requirement absent from every task as `Must fix`. -