## Summary

<!-- 1-3 sentences (or a few crisp bullets): what changed and why. Name the ADR or issue if one applies. Write so a reviewer grasps it in ~15 seconds. -->

## Changes

<!-- One line per change: `path/or/area` — what changed, declaratively (verb + what + where). State the fact and let the diff carry detail. For many sub-items, give the shape and count ("add 21 trigger phrases") instead of listing each. -->
- `path/or/area` — what changed

## Notes

<!-- Omit this section for routine PRs (drop it when nothing qualifies). Note it here when a trigger applies, one terse declarative line per point: a non-obvious decision, a deliberate omission, a follow-up, a gotcha, a "supersedes #N". Also note it when a RISK/VERIFICATION trigger holds — manual verification was performed; part of the change sits outside CI coverage; migration/rollout ordering matters; a security-sensitive surface changed (e.g. `Not covered by CI — terraform plan is manual`). State the caveat as one fact; let CI carry command output. Skip what is always true (a PR can be reverted; CI runs the tests). -->
