<!--
See .agents/skills/writing-style/pull-requests.md for the prose rules.

Lead with what changes, then why. Keep the measured results, constraints, and
caveats a future reader needs; length follows useful content rather than a fixed
limit. Do not add Summary/Changes/Testing headings, an implementation inventory,
checkboxes, attribution, or validation narration. If an issue exists, end with
"Fixes #NNNN" or "Part of #NNNN".

Example:

Normalize DAPO loss over all response tokens instead of normalizing each
example separately. Per-example normalization over-weights short responses,
hurting math tasks where correct answers need longer derivations.

Fixes #1234
-->
