spec-validatelisted

# Spec: Validate ## Overview Validate audits the full `specs/` directory against the codebase and produces a structured gap report. It runs without clarification — audit first, questions after. Do not ask the user anything before producing the report. ## Severity Levels - **Critical** — rebuild from specs would produce wrong behaviour - **Gap** — rebuild would produce incomplete behaviour - **Drift** — spec and code have diverged but rebuild intent is recoverable ## The Nine Categories Check every category, in order. Do not skip any. Report findings under the appropriate severity. ### 1. Missing capability specs Code areas with no corresponding spec file, or not listed in `specs/README.md`. *How to find:* scan `src/` (or equivalent) for functional areas; cross-reference with `specs/`. *Severity:* Critical if a core area; Gap if peripheral. *Referral:* `spec:infer` ### 2. Outdated decisions Spec entries contradicted by current code. *How to find:* for each Decision entry, verify the described behaviour exists in code. *Severity:* Critical if the contradiction would produce wrong rebuilt behaviour; Drift if intent is recoverable. *Referral:* `spec:maintain` if from a recent change; `spec:infer` if drift is older or scope is unclear. ### 3. Unconfirmed inferences Remaining `> Inferred — please confirm` markers in any spec file. *How to find:* grep `specs/` for `> Inferred`. *Severity:* Gap — the entry has not been validated by a human. *Referral:* review directly with t