## What changed
Describe the change functionally — what behavior changes and its impact on users
or callers. Lead with outcomes; don't walk through code locations, the diff shows
where and how. Keep any code-level notes short and specific.
## Why
Problem or motivation.
## Before / After
Show the effect with evidence. Include before and after whenever behavior changes —
CLI/API output, logs, metrics, or screenshots for UI (attach working screenshots
when possible). For changes with no observable behavior (pure refactor, docs), say so.
## Risk
- Low / Medium / High
- What can break
## Checklist
- [ ] Tests added or updated
- [ ] Backward compatibility considered
- [ ] Knowledge concepts updated, or no update required with a reason
## Knowledge
Updated concepts, or `No knowledge update required — <reason>`.
## Security
Security review and relevant threat-model categories, or why no security-relevant code changed.
## Follow-ups
List deferred work with rationale, or `No follow-ups.`