## Summary

Describe what changed and why.

## User-facing changes

Describe the behavior visible to users, or write `None` for internal-only changes.

## Release notes

Maintainers: apply the most appropriate release label before merging. Use
`skip-release-notes` only when this pull request should not appear in a release.

- `breaking-change`
- `enhancement` or `feature`
- `bug` or `fix`
- `performance`
- `security`
- `dependencies`, `build`, or `ci`
- `documentation`

## Verification

Describe the tests or checks performed.