Review this change for correctness. I want the bugs, not a style pass.

What to review: [THE DIFF, BRANCH, PULL REQUEST OR FILES]
What the change is meant to do: [ONE OR TWO SENTENCES, OR THE TICKET TEXT]

## Before you judge

Read every changed file in full, not only the changed lines. Read the callers of anything whose behavior or signature changed, and the tests that cover it. If you only have the diff and need more to be sure, ask for the file instead of assuming what it contains.

## Look for, in this order

1. **Bugs:** wrong logic, wrong conditions, off-by-one errors, null or undefined values, wrong types, race conditions, broken callers.
2. **Broken edge cases:** empty input, zero, very large input, duplicates, retries, time zones, concurrent requests, partial failure.
3. **Missing error handling:** swallowed errors, unchecked results, no timeout, no rollback, failures the user never sees.
4. **Security:** unvalidated input, injection, missing authorization checks, secrets in code or logs, data shown to the wrong user.
5. **Missing tests:** changed behavior with no test, or tests that would still pass if the code were wrong.
6. **Intent:** compare the change with what it is meant to do, and name anything missing or extra.

## Report each finding like this

- **Severity:** blocker (wrong result, data loss, security), major (fails in a realistic case) or minor (unlikely, or low impact)
- **Where:** file path and line
- **What fails:** a concrete scenario: this input or this sequence, the result now, the result expected
- **Fix:** the smallest change that solves it, as a short snippet or a clear description

Start the reply with one line: the count per severity, and whether you would merge it. Then list the findings, blockers first.

## Do not

- No style, naming or formatting comments, unless the style hides a bug. If it does, say which bug.
- No finding without a failure scenario. If you cannot describe how it breaks, put it under "Questions", not under findings.
- Do not report a bug because you did not read the code that handles it. Check first.
- Do not pad the list. If you find nothing, say "No correctness problems found", then list what you checked.
- Do not edit any file. This is a review.

End with "Not verified": anything you could not confirm, such as code you could not see or tests you could not run.
