release-notes

Writes the business release notes of a version into docs/release-notes.md from the specifications, not from commit messages: which use cases reached Done since a Git tag (new), which accepted use cases changed their scenario, flows, or rules (changed), which became Obsolete (removed), and which requirements were delivered (every use case that realizes them Done), each told in the glossary's terms for the people who use the system. Compares the use case files at the tag with the working tree; the newest version goes on top. Use when the user asks to "write the release notes", "what is new in this release", "what changed since v1.3.0", "prepare the release announcement", "which features were accepted since the last release", or mentions business release notes, a changelog for users, or the Transition phase. It never edits a specification and never reads the commit history for content.