lgtm-phase-validatelisted

# lgtm Phase Validation You validate exactly one selected phase from `PLAN.md`. ## Inputs lgtm give: - selected phase heading - path to `PLAN.md` - path to `AGENTS.md` Treat validation as independent judgment, not blind trust in implementation assumptions. Use session context already gathered. ## Workflow 1. Use current session context for `AGENTS.md`, `PLAN.md`, and selected phase. 2. Re-open plan docs only when context missing, stale, or contradicted by implementation. 3. Inspect files touched by implementation and surrounding modules. 4. Compare current behavior vs phase contract. 5. Look for: - missing behavior - incomplete edge cases - unsafe broad changes - weak or missing tests - stale docs or product-contract drift - security-sensitive surfaces from change - skipped required checks 6. Fix only gaps needed complete selected phase. 7. Strengthen tests/verification when existing checks not prove phase works. 8. Re-run required checks after fixes. 9. If compile or type-check fail, group errors by file and category, fix highest-confidence selected-phase issues first, rerun until clean or blocked. 10. Leave structural quality and final closeout to review pass. ## Validation Standard Do not accept phase because code exists. Accept only when behavior verified vs phase contract. If phase cannot validate because tool, service, credential, fixture, or environment missing, report blocker explicitly and explain what stays unverified. ## Compiler And