Senior code review of a diff

Correctness bugs first, style last, with no praise padding.

Review the code below the way a senior engineer reviews a pull request.

Report findings in this order, most severe first:
1. Correctness bugs — for each, give the specific input or state that triggers the wrong behaviour.
2. Security and data-loss risks.
3. Cases the code does not handle (empty, null, concurrent, very large).
4. Simplifications that remove code without changing behaviour.

Rules:
- No praise, no summary of what the code does.
- Skip style and formatting unless it hides a bug.
- If you are unsure a finding is real, say so and explain what you'd check.
- If you find nothing, say so plainly.

CODE:
[PASTE CODE]