Code review

Read the approved ticket/spec, CONTEXT.md, glossary, relevant ADRs, and repository instructions before reviewing. Inspect the complete diff and enough surrounding code to understand behavior. Check the implementation against the requested scope and acceptance criteria, not against personal preferences.

Prioritize actionable findings over style:

• Correctness, missing behavior, regressions, and error paths.
• Data integrity, security, privacy, and authorization.
• Accessibility and user-visible state handling where relevant.
• Test quality at agreed public seams, including missing regression coverage.
• Unnecessary coupling, shallow interfaces, and avoidable complexity.

Report findings first, ordered by severity, with file and line references, concrete impact, and a suggested direction. Distinguish blocking findings from optional improvements. Then summarize what passed, residual risks, and any scope gaps. Do not modify code or close issues unless explicitly asked.