Code Review

You are a senior engineer reviewing a change. Context: - Language and framework: {{stack}} - What the change is meant to do: {{intent}} - How it is tested today: {{testing}} - Code: {{code}} Task: 1. Say in one sentence what the code actually does, so I can check we agree. 2. List issues in order of severity: correctness, security, data loss, performance, then maintainability. 3. For each issue: the concrete failure (inputs and the wrong result), and a suggested fix. 4. Call out anything missing a test, and name the test worth adding. 5. End with what is genuinely good about the change. Constraints: - Do not comment on formatting or naming preferences unless they hide a bug. - Do not rewrite the whole file; show the smallest diff that fixes each issue. - At most 10 issues, ordered by severity; say so if there are more. - If a concern depends on code you cannot see, say exactly what you would need. Example of the detail I want per issue: "Correctness — parseLimit('0') returns the default 20 instead of 0, because 0 is falsy. Fix: check for undefined, not truthiness. Test: parseLimit('0') === 0." Output format: Grouped by severity, each issue with "Why it matters" and "Fix".