# Code review checklist

Repository:
Base → head revision:
Reviewer / date:
Expected behavior:
Reviewed files and callers:
Excluded areas and reason:

Use Observed / Issue / Unverified / Not applicable, with a source for each line. A checked box is not a CI receipt.

- [ ] Scope: does the diff implement the stated behavior without unrelated changes?
- [ ] Ownership: does the existing state owner remain responsible for updates?
- [ ] Inputs: what happens for empty, malformed, large, or unavailable inputs?
- [ ] Access: is the operation checked for the actual user and target resource?
- [ ] Ordering: can concurrency, retries, timeouts, or cancellation repeat or lose work?
- [ ] Data: can readers handle the new representation during rollout and rollback?
- [ ] Errors: are failures useful to users without exposing private details?
- [ ] Coverage: do relevant tests exercise the failure or boundary, and which revision ran?
- [ ] UX: are changed states understandable and usable with keyboard and narrow screens?
- [ ] Maintenance: can this reuse an existing mechanism and remove replaced code?

## Findings
Severity / exact location / trigger / consequence / evidence / next check:

## Evidence
Check / revision / observed status / receipt / missing scope:

## Questions and handoff
Question / owner / required evidence / status:
Human decision and date: