# PR Checklist

- Scope stayed small and reviewable.
- Existing project patterns were reused before introducing new abstractions.
- Intended files and allowed change types still match the actual change.
- Behavior changes include updated or new tests.
- Required commands for the task were actually run.
- The evidence note exists and matches the completed task.
- Review-critical paths, config changes, or interface changes are called out explicitly.
- Risks, assumptions, and follow-ups are documented in the PR description.
- The project state file was updated if the task changed the next action materially.