Pull Request Standard

Required PR content

A PR explains the problem, solution, test evidence, risk, rollout impact, and rollback approach. It links the work item and identifies breaking API, configuration, database, or infrastructure changes.

## Summary
## Why
## Changes
## Test evidence
## Security and data impact
## Deployment / configuration impact
## Rollback
## Checklist
- [ ] Tests added or updated
- [ ] Documentation updated
- [ ] No secrets or sensitive data
- [ ] Backward compatibility considered

Review expectations

Reviewers evaluate behavior, design, security, tests, operability, and maintainability. “LGTM” without meaningful inspection is not sufficient evidence. Authors respond to feedback or explicitly explain why a suggestion is not adopted.

Size

Prefer PRs below roughly 400 changed lines excluding generated files, but do not game the metric by splitting a coherent change into unsafe pieces. Large changes include a review plan and are broken into independently safe stages where possible.