Ship code with AI

I need a plan, not code yet, for the following change.

Ticket / problem statement:
"""
{{paste ticket or 1-paragraph description}}
"""

Repo context:
- Language / framework: {{e.g. TypeScript + Next.js 16 App Router}}
- Where the change probably lives: {{e.g. lib/auth, app/api/billing}}
- Constraints I care about: {{e.g. no schema migration this week, must stay backwards compatible with v1 clients}}

Output, in this order:
1. **Restated problem** in 2 sentences (so I can confirm we're solving the right thing).
2. **Files to touch** as a bulleted list with a 1-line "why" each.
3. **Smallest viable diff** in 5 to 8 bullets describing the change.
4. **Edge cases** the diff has to handle (3 to 5 specific ones).
5. **What I should NOT change** to keep the PR small.

If the request is ambiguous, ask 1 to 2 specific clarifying questions before the plan.

Implement the plan below. You have file system access in this repo.

Plan:
"""
{{paste the plan from step 1}}
"""

Rules:
- Smallest viable diff. No drive-by refactors, no rename-while-you're-there.
- Match the existing code style: imports, naming, error handling. Read 2 to 3 nearby files before introducing a pattern that's new to this repo.
- No new dependencies unless the plan explicitly called for one.
- If you add a test, place it next to the existing tests and match their style.
- Run the test command before reporting done. If a test fails, fix it before stopping.

When done: print a 2-line summary of what changed and the list of files touched.

You are fixing a code review finding.

CodeRabbit comment:
"""
{{paste the inline comment, including the line number and severity}}
"""

The file the comment is on (full file or the relevant 80-line region):
"""
{{paste file region}}
"""

Repo context:
- Language / framework: {{e.g. TypeScript + Next.js 16 App Router}}
- Test framework: {{e.g. Vitest, Jest, none}}
- Style conventions worth preserving: {{e.g. server components default, no class components}}

Output, in this order:
1. **Diagnosis** — one sentence. What is actually wrong, and why CodeRabbit flagged it.
2. **Patch** — a unified diff against the file region above. Minimal change. No drive-by refactors.
3. **Test** — if the change is non-trivial, the test that would have caught it (in the project's test framework). Skip if the project has no test setup.
4. **Reply for the PR** — 1 to 2 sentences I can paste under the CodeRabbit comment to resolve it.

Do not modify code outside the diff. Do not invent imports.