## PR Type
- [ ] Spec only
- [ ] Implementation
- [ ] Bugfix
- [ ] Release/docs/process
## What
Brief description of changes.
## Why
Why is this change needed?
## Issue Links
- Refs #
- Closes #
Spec-only PRs must use `Refs #...`, not `Closes` / `Fixes` / `Resolves`,
unless the linked issue is explicitly only about writing the spec. Runtime or
user-visible work must close an implementation issue, not a spec issue.
## Spec Lifecycle
- [ ] If adding/updating `docs/specs/<id>/`, updated `docs/specs/README.md`
- [ ] If this is spec-only, linked or created implementation issue(s)
- [ ] If this is implementation, updated relevant spec, README, API docs, or wrote why not needed
- [ ] If touching `src/api/**`, updated `docs/specs/SPEC-web-api.md` or wrote an explicit API docs waiver with rationale
## Test Plan
- [ ] Tests pass
- [ ] Tested manually
## Review
- Final head SHA:
- Reviewer:
- [ ] Actionable review findings and conversations are resolved
- [ ] Security review completed when the change affects a security boundary
## Merge Authorization
- [ ] Applicable ordinary CI checks are green on the final head
- [ ] Normal maintainer review is complete
- [ ] Explicit human merge authorization is recorded
- [ ] Release authorization will be obtained separately when applicable