<type>[optional scope][!]: <imperative summary>

; A retained logical commit is the portable change record for Git-only readers.
; Keep these four column-zero headings exactly once and in this order. One
; large atomic commit is valid; keep detail proportional to the change.
; Begin the body here without a nonblank preamble. Raw HTML is not accepted;
; put literal HTML or comment examples in a fenced code block.
## Summary

- <Describe the observable change and why it is needed.>

## Boundaries and compatibility

- <Record important invariants, non-goals, and compatibility impact.>
- <Record migration, rollout, or release details when applicable.>

## Investigation

- <Point to useful repository-local modules, tests, ADRs, issues, or docs.>

## Validation

- `<command>`: <result>

; Keep multiple independent commands or results as separate top-level `- `
; list items. One clean aggregate from one command remains one result. If it
; was not run, give a specific reason.
; Keep every section and remove every template token.
; PR metadata supplements this body. Wrap commit prose at about 72 columns;
; use natural Markdown without artificial hard wrapping in PR descriptions.
; Add `BREAKING CHANGE: <impact and migration>` below Validation when useful.
; Add issue trailers such as `Closes #3` last.
