pr-packagelisted

# PR package An unattended run moves the human's attention from during to after. This document is what they attend to. Written well it takes five minutes; written as a change log it takes forty and the ledger goes unread. Lead with what needs a decision. What was built is context; what you decided on their behalf is the thing only they can approve. ## What goes in ```markdown ## What and why <Two or three sentences. What a user can now do, and why. Link the ticket and docs/specs/<id>.md.> ## Decisions I made for you <The ledger, surfaced — not linked. Each entry: what was decided, the alternative, why this one, and the cost of being wrong. Highest reversal cost first. This is the section that must be read; put it above everything else.> ## Evidence <Per acceptance criterion: the test, the screenshot, or an explicit "unverified" with its blocker. Gate results as exit codes. Screenshots inline for every user-visible state.> ## Review guide <Where to start reading, and which part deserves the most attention. Name the file that carries the real logic. The rest is scaffolding and can be skimmed.> ## Risk and rollback <What could break, who would notice first, how to revert. Whether it is behind a flag. Whether it needs a backend deploy first — version skew, honestly stated.> ## Noticed but not done <Everything out of scope that is now known: adjacent bugs, debt found, the shared lib that wants refactoring. Each with enough detail to become a ticket.> ## Unverified <Every