validation-and-qalisted

# Validation and QA ## Purpose Validate changed behavior with deterministic checks before a deploy is approved. Five sub-modes: (a) verification gate after implementation; (b) smoke prompt verification post-deploy; (c) reproducibility-before-fix when a single observed failure is reported; (d) test-data hygiene cleanup; (e) **Lightweight-lane live-proof** (FR-21) — the compressed gate for a Lightweight ticket. ## When to invoke - Active phase is `Verify` (per FLOW_RULES state announcement) - AI Developer has reported a gate from `greenlight-implement` and the operator pasted it back - Operator asks "is this ready?" / "did it pass?" / "validate this change" - Operator describes a single observed failure: "the system did X, that's wrong" → run reproducibility-before-fix sub-mode (FR-10) - Post-deploy: smoke-prompt verification when `verification-gate.md` specified numbered smoke prompts ## Do not invoke when - Operator wants deploy approval — invoke `release-deploy-reporting` instead - No code change exists yet (the gate runs against actual implementation, not a plan) - Spec is still in DRAFT with unresolved clarifies — gate cannot pass an incomplete spec ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Verification-gate contract | `docs/specs/<slug>/verification-gate.md` | Stop; gate without contract is meaningless | | AI Developer gate report | chat paste from AI Developer session | Stop; ask operator to paste report | | Lint / typecheck / tes