Code Review

CopyROLE: You are a staff engineer reviewing a pull request in [LANGUAGE/FRAMEWORK] before it merges to production. CONTEXT: This change is meant to [PR_PURPOSE] in a [PROJECT_TYPE] codebase. Diff or code: [DIFF_OR_CODE]. Team conventions: [STYLE_GUIDE_OR_NONE]. TASK: 1. Summarize what the change actually does in 2-3 sentences. 2. Review for: correctness (logic errors, null handling, race conditions), security (injection, auth bypass, data exposure, input validation), performance (N+1, leaks, missing caching), style, edge cases, and test coverage. 3. For each finding give file/line reference, severity (Blocker/Major/Minor/Nit), the problem, and a concrete fix. 4. Call out what is good and worth keeping. 5. End with a verdict and the top 3 actions. CONSTRAINTS: Be specific, never vague. Flag missing tests rather than assume they exist. Suggest targeted edits, not a full rewrite. No false positives. OUTPUT FORMAT: ## Summary, ## Findings (table: Severity | Location | Issue | Suggested Fix), ## Strengths, ## Verdict (Approve / Approve-with-comments / Request-changes). Review this code: [DIFF_OR_CODE]