## Problem and resulting behavior

[Concrete trigger, previous behavior, and resulting behavior.]

## Scope and references

- Owning task / coordinating issue:
- Relevant design or contract:
- Cross-repository dependencies / required release order, if any:

## Verification

[Commands actually run and observed results. State a material skipped check and its reason; do not mark planned tests as passed.]

## Compatibility and operations

[API/data/package impact, rollout and recovery where applicable. Remove when irrelevant.]

## Documentation

[Affected authoritative docs updated, or why none change.]