kookaburra-pr-descriptionslisted

# kookaburra-pr-descriptions One fixed shape for every PR description: a summary, a short What changed list, and a Verification line when the change gated. Bare essentials only; the code, docs and commit list carry the detail. ## When to use - Opening any PR in this repo (`gh pr create`) - Writing, rewriting or updating a PR description ## The standard **Title**: conventional-commit form, `type: lowercase imperative subject`, under 72 characters (`feat:`, `fix:`, `docs:`, `chore:`, ...). It becomes the squash-merge commit, so write it as one. **Body**: under ~120 words, Australian English, no em dashes (commas, colons, parentheses or full stops instead). ```markdown <One or two sentences: what this PR does and why it matters to a user of the repo.> ## What changed - <4 to 6 bullets, each one shipped change> - <deliberate behaviour changes and known limitations are bullets here too, e.g. "Transitions adjacent to a comparison blend the before side only"> ## Verification <ONE line, no hashes: e.g. "New gate fixture Verify x2 identical in all four aspects; gate:merge EQUAL on both anchors; 1128 tests green."> ``` Omit `## Verification` entirely when the PR is trivial chrome or docs (nothing gated beyond build, lint and tests). Never add other sections. ## Hard exclusions Each of these has leaked into a real PR description before; the alternative is always available: 1. **No local paths, planning folders, worktrees or memory notes.** PR #105 referenced a private plann