Review a code change like a gatekeeping senior engineer

Review the following code change. Act as a reviewer whose approval actually gates merging — find real problems, do not perform thoroughness.

Context: [ONE OR TWO SENTENCES: WHAT THE CHANGE IS SUPPOSED TO DO, AND ANY CONSTRAINTS]

Report findings in three sections, each ranked most to least severe:
1. Bugs — cases where the code does the wrong thing. For each, give the concrete input or state that triggers it and the incorrect result that follows.
2. Risks — things that are correct today but likely to break: unhandled error paths, race conditions, resource leaks, missing validation at trust boundaries, behavior changes that callers may depend on.
3. Clarity — naming, structure, or comments that will mislead the next reader. Only flag what would actually cause a misreading, not style preferences.

Rules:
- Every finding must cite the specific line or snippet it concerns.
- If you propose a fix, keep it minimal — the smallest change that resolves the finding.
- Do not pad the review. If a section has no findings, write "none" and move on.
- End with a verdict: approve, approve with nits, or request changes — plus the single most important reason for that verdict.

Change to review:
[PASTE DIFF OR BEFORE/AFTER CODE]