## Summary

<!--
The smallest view that makes the change clear, next to short text: pseudocode, a call or file
tree, a diff sketch or a Mermaid diagram. Reference the issue, e.g. "Closes #123". Sections follow
the pr skill, see ai/skills/engineering/pr/SKILL.md.
-->

## Evidence

<!-- Before and after: a failing and passing test run, console output or a screenshot. -->

## Merge Danger

**Door:** <!-- one-way or two-way: can the change be walked back cheaply? -->

**Blast Radius:** <!-- one word: who or what is affected if it goes wrong -->

<!--
Optional, when they apply:
**Breaking:** what users, configurations or integrations must change.
**Security:** what the change means for security.
-->

## Checklist

- [ ] AI-assisted (an agent wrote or co-wrote part of this PR)
- [ ] I reviewed the complete diff myself (author review)

<!--
If the pull request is AI-assisted, CI requires the section below with the full SHA of the head
commit in its Reviewed: line. The agent writes the section from its self-review of the current head
commit. Before every push, rerun the self-review and rewrite the section, do not just edit the
SHA; replace the body right after the push. See docs/develop/ai.md.
Delete the section if the pull request is not AI-assisted.
-->

## Self-review