pr-and-issue-disciplinelisted

# PR and Issue Discipline > Show the change before telling it: real captured output first, the fewest words after, drafts that flip ready on convergence and back on commit-requiring work, and a human hand on the merge by default. These rules apply to any session that opens or updates a PR or writes an issue. "The author" below is whoever prepared the change, human or agent, working alone or in a multi-agent session. ## When to Apply - Opening or updating a pull request (body, title, draft state) - Writing a bug report or issue - A review round just landed on an open PR - Deciding whether a PR merges, and by whose hand ## PR Bodies: Visualization First The opening section is real captured output, not prose. A reader must get the change from the fenced blocks without reading a paragraph. ````markdown ## The bug this kills (or "## What this adds" for a feature) Before: ```text $ bun run check scripts/sweep.mts: probe timed out after 120s; agent marked dead (it was mid-build) ``` After: ```text $ bun run check scripts/sweep.mts: probe extended 120s -> 300s while the build lock is held; agent alive ``` ## How ```text before: probe start -> fixed 120s -> timeout -> agent marked dead (mid-build) after: probe start -> 120s up -> build lock held? -> extend to 300s -> live verdict ``` ## Proof - 34 tests green (2 new), `bun run check` green, CI watched to completion - 2 review rounds, every thread resolved ```` - The opening blocks are actual commands and actual