PR writeup · [PR title]

What changed

[Primary change in one line]
[Secondary change, if any]
[Behavioral change a user/agent would notice]

Why

[The problem this PR answers — reference the bead / PRD / SPEC it lands, and the decision it implements. One paragraph max.]

How

[Implementation shape in 2-4 bullets: main files touched, the seam chosen, what was NOT changed on purpose.]

[File/area] → [what changed and why that layer]
[File/area] → [what changed and why that layer]
[Explicitly untouched] → [so reviewers do not hunt for a ghost]

Tested

Check	How	Result
[behavior]	[command / manual step]	PASS / FAIL
[behavior]	[command / manual step]	PASS / FAIL
[regression surface]	[test suite run]	PASS / FAIL

Screenshots

Inline images only (embedded directly in this self-contained file); never hot-linked.

[ Screenshot 1 — before ]

[ Screenshot 2 — after ]

Living + @hash URLs

Publish with tot. The living URL tracks the branch tip; the @hash URL freezes this exact commit so a link in a review or comment never rots. Paste both into the PR description.

tot: tot/<owner>/<repo>/<slug> (living — branch tip)
tot: tot/<owner>/<repo>/<slug>#@<sha> (@hash — frozen)

Security: if the writeup contains anything sensitive, share the file path instead of a tot link ("link is the key" is for non-sensitive artifacts only).

Canonical source

The markdown source of record for this writeup lives at docs/plans/...[slug]-pr-writeup.md (see the <meta name="source"> header of this file). Edit the .md; regenerate this render. Drift between this page and the source is a bug.