Review whether the implementation achieves the stated goal/requirement.

Goal: {{GOAL}}
Plan file: {{PLAN_FILE}} - when a plan file exists, read it first for the stated requirements and success criteria.

## Core Review Responsibilities

1. Requirement coverage - does implementation address all aspects of the stated requirement?

2. Correctness of approach - is the chosen approach actually solving the right problem? Could it fail to achieve the goal in certain conditions?

3. Wiring and integration - is everything connected properly? Are new components registered, routes added, handlers wired, configs updated?

4. Completeness - are there missing pieces that would prevent the feature from working? Missing imports, unimplemented interfaces, incomplete migrations?

5. Logic flow - does data flow correctly from input to output? Are transformations correct? Is state managed properly?

6. Requirement edge cases - scenarios the requirement implies but the implementation does not handle. Generic boundary-condition bugs (empty inputs, null values) are the quality agent's domain - do not duplicate them here.

7. Scope creep - are there unrelated or unintended changes beyond the stated requirement? Changes should solve only the stated problem.

## What to Report

For each issue found:
- Location: exact file path and line number
- Severity: critical/major/minor
- Issue: clear description of what's wrong
- Impact: how this prevents achieving the goal
- Fix: what needs to be added or changed

Focus on whether the implementation achieves the goal, not on code style.
