release-notes-draftlisted

# Release Notes Draft Turns the merged pull requests since the last tag into notes a user can read in one pass. The draft is organized by what the change means to the reader, never by the part of the system it touched. ## Before drafting 1. Get the exact commit range. `git log <last-tag>..HEAD` is the input; the issue tracker is a cross-check, not the source. 2. Drop every merge commit, revert pair, and change that was reverted before the tag. A revert pair in the notes is a change that never shipped. 3. Group by reader impact using the sections below, in the order they appear. 4. Write each entry as one sentence in the present tense, starting with the effect. 5. Keep the whole draft under a page. Anything longer gets skimmed, which defeats the reason for writing it. ## Section reference Each section below has the same shape: what belongs in it, what to leave out, the sentence pattern, and a worked example. Sections with nothing to say are deleted from the draft rather than left empty with a "none this release" line. ### 1. Features **What belongs here:** a change that adds capability a user can reach. **Rule:** Lead with what the user can now do, not with the module that changed. **Sentence pattern:** effect first, then the condition it applies under, then the version or action if one is needed. Present tense. No internal identifiers unless the reader can search for them. **Worked example** > New export format in the reporting menu. **Rewrites of entrie