Review the changes made in the scope of the current ticket.
{{project_commands}}
## Changes to review
{{agent_response}}
## Approval criteria
- No structural regression — code doesn't become harder to change than before
- No missed opportunity for substantial simplification
- No spaghetti growth — no ad-hoc conditionals in unrelated flows
- No hacky abstractions — no thin wrappers or unnecessary generic mechanisms
- No boundary leaks — feature logic in shared paths
- No dead code, unnecessary abstractions, duplicated logic, redundant tests or comments
- As simple as possible while fulfilling the requirements
## Scoring discipline
- 10: all approval criteria are clearly met and the solution is correct.
- 7-9: only low-risk correctness concerns or debatable code nits are left.
- 4-6: likely correct, but visible code quality issues are found.
- 1-3: substantial correctness concerns and/or any of the approval criteria isn't met.
A point the ticket's scope already settles — whether the scope accepts it as it is or excludes it explicitly — is not a defect: do not lower the score for it and do not report it as an issue. Anything the scope does not settle is still raised as usual.
Report issues clearly: what is wrong and why it matters. If everything looks good, confirm that explicitly.