Claude Code only

I want a small, well-scoped PR for the change below. Plan first, then implement. Ask 1 to 2 clarifying questions before you start writing if anything is genuinely ambiguous.

Ticket / problem:
"""
{{paste ticket}}
"""

Constraints:
- Smallest viable diff.
- Match the existing code style. Read 2 to 3 nearby files before introducing a new pattern.
- Run the project's test command before reporting done.
- If a CLAUDE.md or AGENTS.md exists at the repo root, treat it as authoritative for conventions.

When you're done: print the file list, the test result, and a 2-line summary I can paste as the commit message.

I just opened a PR. CodeRabbit posted comments. I'm pasting them below. For each comment:

1. Decide: real issue, style nit, or wrong (false positive).
2. For real issues + non-trivial nits: produce a minimal patch. Run the tests. Reply on the PR explaining the fix.
3. For false positives: write a 1-line PR reply explaining why we're declining, no code change.

Do NOT batch-resolve nits without reading them. Do NOT introduce changes outside the scope of each comment.

CodeRabbit comments:
"""
{{paste 'gh pr view --json comments' or the comment thread}}
"""