code-quality-checklisted

# Code Quality Check Used during the "Retrofitting an Existing Project" workflow (see AGENTS.md). Run this immediately after Step 1 (Read Codebase) and before Step 2 (Documentation). Do not begin writing documentation until all High severity issues have been resolved. **Also run this in full — not the lightweight Checkpoint A questions — whenever the user confirms this code needs a full quality review** (asked because there is no project record of who built it or whether it was reviewed — not because of a guess about whose code it is; see `guidance/learning-checkpoints/common.md` → Checkpoint A for the exact ask-first trigger). In this case each finding must also include the two extra fields defined under **Report Format** below (Why It's Wrong / Correct Pattern) — the point is for the person reviewing it to learn from the findings, not just get a fix list. --- # Required Context Read the documents for your declared project type before inspecting code. **Hybrid projects (e.g. `Data Pipeline + Web App`):** there is no combined row below — read and apply every row for each declared type, union the "What to inspect" and Layering rules across them, same as the guidance-file rule in `AGENTS.md`. | Project type | Read before inspecting | |---|---| | **Web App** | `current-state.md`, `docs/architecture/*`, `docs/business/*`, `docs/specs/data-model.md`, `docs/specs/permissions.md`, `docs/project-plan.md` | | **Microservices** | `current-state.md`, `docs/architecture/*`, `docs