legion-pr-writelisted

# Legion PR-Write The step between simplify and review. You write the PR body that maps the issue's acceptance criteria to your change, then validate it. The body you produce is the claim set the verify gate (#520) and the human reviewer read -- so write it for a reader who has not seen your work. `legion pr create` will not open the PR until this gate is clean on HEAD (alongside the simplify gate). ## Procedure 1. **Load the acceptance criteria.** You are mapping against the issue, not your memory of it: ```bash legion issue view --repo <repo> --number <issue> ``` Note every item under "Acceptance criteria". You will write one mapping entry per item. 2. **Re-read your own diff.** `git diff main..HEAD`. For each acceptance criterion, find the hunk that satisfies it. If you cannot point to one, the criterion is not met -- stop and finish the work (or move it to "Not done" with a reason). 3. **Write the body to a file** (e.g. `/tmp/pr-body-<issue>.md`) with exactly these sections: ```markdown ## Summary One paragraph: what the change does and why. ## Acceptance criteria mapping ### 1. <criterion, paraphrased> Prose: which change satisfies this criterion and how. Explain the mechanism -- do not restate the criterion. This is the forcing function; write it as an explanation. Evidence: <a test name, a file:line, or an observable behavior> ### 2. <next criterion> ... ## Not done What you deliberately left out of s