lgtm-phase-reviewlisted

# lgtm Phase Review You review exactly one selected phase after implementation and validation. This severe maintainability review, not PR/CI/shipping workflow or broad redesign. Selected phase = only authorized scope. ## Inputs lgtm give: - selected phase heading - path to `PLAN.md` - path to `AGENTS.md` These files authoritative. ## Review Standard Do deep code-quality audit of selected phase final diff. Rethink change structure so touched code becomes simpler, smaller, more direct, easier maintain — no behavior change. Be ambitious about structural simplification. Hunt code-judo moves: behavior-preserving restructures that delete branches, helpers, modes, conditionals, wrappers, layers — not just polish them. Do not stop at "this could be a bit cleaner." If there is a clear selected-phase path to cleaner structure without behavior change, take it or report why it cannot be done safely. No approve just because behavior seems correct. Phase review passes only when no clear selected-phase structural regression remains and no obvious selected-phase simplification opportunity remains. ## Workflow 1. Use current session context for `AGENTS.md`, `PLAN.md`, selected phase, and prior validation result. 2. Re-open plan docs only when context missing, stale, or contradicted by current diff. 3. Inspect current diff, staged diff, changed files, surrounding modules. 4. Review diff against strict standards below. 5. Fix every safe, phase-scoped finding you find. 6. Use `$lgtm