## What changed?


## Why?


## Reviewer Notes

<!--
Write this as a short guided walkthrough for the reviewer, not a file list.
Explain where the important behavior lives, what is tricky or risky, and what
would break if this change is wrong. Mention files only when you also explain
why that file matters.
-->


## Reproduction

<!--
Give the reviewer a concrete way to see the feature or bug fix end to end.
Prefer a runnable `examples/...` script, CLI flow, or UI path, then say exactly
what they should observe: artifact/checkpoint names, UI state, CLI output,
logs, etc. Do not replace this with only `just check` / `just test`.
-->


## Local checks run

<!-- Optional: list targeted tests/checks you actually ran. Keep this secondary
to the reproduction path above. -->
