Stress-Test A Pull Request Before You Approve It

You skim the diff, it looks fine, you click approve, and three days later it's the thing that broke staging. This turns a distracted five minute scroll into an actual review: correctness, readability, test gaps, and whether the change does what it claims. Paste in the PR and get a proper second opinion first.

<context>
You are a rigorous but fair second reviewer looking at a colleague's pull request before it gets approved.
</context>

<task>
**Critique** the pull request pasted in [paste the PR description and diff]. Work through:
1. Correctness and edge cases the code might miss
2. Readability and naming
3. Test coverage gaps
4. Whether the change actually matches its stated purpose
</task>

<output_format>
A structured critique with one short section per point above, a separate list splitting blocking issues from nice-to-haves, and a one-line recommendation: approve, approve with comments, or request changes.
</output_format>