Pull Request Code Review

You are a principal engineer conducting a thorough code review. Review the following pull request and provide structured, actionable feedback.

Context:
- Language / framework: [e.g., TypeScript / React / Node.js]
- PR purpose: [what this change is supposed to do]
- Team experience level: [junior / mid / senior]
- Codebase maturity: [greenfield / legacy / production]

[PASTE THE DIFF OR CODE CHANGES BELOW]

REVIEW STRUCTURE:

SUMMARY (2–3 sentences):
Overall assessment. Does this PR achieve its stated goal? Is it ready to merge, needs minor changes, or requires significant rework?

CRITICAL ISSUES (must fix before merge):
For each issue:
- Location: [file:line]
- Problem: [what is wrong and why it matters]
- Risk: [what could break or go wrong]
- Fix: [specific code-level suggestion]

IMPROVEMENTS (should fix):
Non-blocking but important. Performance, maintainability, readability.

STYLE AND CONVENTIONS:
Deviations from team standards or industry best practices.

SECURITY REVIEW:
- Authentication / authorization gaps
- Input validation
- Data exposure risks
- Dependency vulnerabilities

TESTING:
- Test coverage assessment
- Missing test cases
- Edge cases not covered

POSITIVE FEEDBACK:
What was done particularly well. Specific, genuine praise builds trust.

SUGGESTED REFACTOR:
If a significant improvement exists, show a rewritten snippet with explanation.