Pr Authoring

Description section — required order

1. End-user point of view first. What does this PR bring to users? New capability, fixed behavior, changed default, …? Call out any implied changes: breaking changes, migration steps, perf characteristics, deprecations.
2. Then justify. Why this change, why this design, main trade-offs considered — enough context for a reviewer to evaluate the approach.

Enrich the description from the checklist

Don't tick the boxes, but use them as prompts to preempt reviewer questions inside the description prose:

• Impact level — minor / patch / major (and mention if pnpm run bump or the changeset bot instructions were followed).
• Single-concern scope — state that the PR is focused, or explain why bundled changes belong together.
• Tests — which tests were added/updated, what they cover, and why they would have failed without this PR. If no tests, say why.
• Gitmoji / scope — the title itself is evidence; no need to restate.
• Understanding of every line — nothing to write, but keep it true.