Release Notes From Git Log, Not From Memory

Step 1: Find the shipped range.
"Find the last deployed release point in this repo: check deployment metadata
or release records first, then tags, release branches, or a CHANGELOG heading.
Do not assume a tag or commit was shipped. If you cannot verify a deployed
range, label the output DRAFT UNRELEASED NOTES and ask me for the range rather
than defaulting to the last 30 days. List every commit in the verified range
with hash and subject line, and tell me what range you chose."

Step 2: Draft grouped by user impact.
"Group those commits into release notes with these sections: New,
Improved, Fixed, Breaking. Rules: describe what the user can now do
differently, not what the code does ('CSV export on the reports page',
not 'refactored exporter class'). Merge multiple commits that ship one
feature into one entry. Put pure chores (dependency bumps, CI,
refactors with no behavior change) in a final Internal section I can
delete. Cite the commit hash after every entry."

Step 3: Verify against the diffs, not the messages.
"For each entry, open the cited commit's actual diff and confirm the
entry doesn't promise more than the code delivers. Commit messages
exaggerate. Flag any entry where the diff shows less than the message
claims, and downgrade the wording to match the diff."

Step 4: Read the Breaking section yourself, twice. That's the one
users screenshot when it's wrong.