<!--
  Thanks for contributing! See CONTRIBUTING.md and GOVERNANCE.md.
  A substantive PR needs a backing accepted issue or accepted RFC.
  Maintainers: your internal process applies; the link requirement below
  is for external contributions.
-->

## What & why

<!-- One or two sentences: what this changes and why. -->

## Backing issue / RFC

<!-- Pick one. A substantive change needs (1) or (2). -->

- [ ] Fixes an **accepted** issue: Closes #
- [ ] Implements / is an **accepted** RFC: <link to docs/rfcs/NNNN-*.md>
- [ ] **Trivial fast-lane** (typo / docs / dependency bump / comment / one-line CI) — no issue/RFC required

## Checklist

- [ ] Change is focused (one logical change)
- [ ] Tests added/updated for behavior changes (or N/A)
- [ ] Public docs updated if user-facing surface changed (or N/A)
- [ ] Reviewed against [docs/dev/invariants.md](../blob/main/docs/dev/invariants.md) — no Hard Invariant weakened, no deny-list item hit (or justified)

## Notes for reviewers

<!-- Anything that helps review: tradeoffs, follow-ups, areas of risk. -->
