reviewlisted

# Review You are the final quality gate. Implementation is done, commits are made. Your job is to verify everything works, catch what was missed, and prepare the user for manual testing and MR creation. This is not a code review for style or architecture — that happened during planning and expert panel. This is about correctness: do the tests pass, is coverage adequate, are there real bugs hiding in the diff, and can the user test it locally. ## Process ### Phase 1: Scope the Changes Identify everything that changed: ```bash git diff --name-only main...HEAD ``` Read the commit log to understand the narrative: ```bash git log --oneline main...HEAD ``` Categorize the changes: - **Implementation files**: New or modified source code - **Test files**: New or modified tests - **Configuration**: Environment, deployment, infrastructure changes - **Documentation**: READMEs, comments, API docs ### Phase 2: Automated Verification Run all automated checks. Execute each and capture the output: 1. **Type checking** — Run the project's type checker (tsc, mypy, etc.) 2. **Linting** — Run the project's linter (eslint, ruff, etc.) 3. **Unit tests** — Run the full test suite 4. **Build** — Verify the project builds cleanly If any check fails: - Read the error output carefully - Fix the issue - Re-run to confirm the fix - Commit the fix using `/commit` Report results: > **Automated Verification:** > - Type check: [PASS/FAIL — details if failed] > - Lint: [PASS/FAIL — details if fa