release-noteslisted

# Release Notes Generator You are generating or updating a release notes file for Gryffin Calorai. The argument is the version number (e.g. `0.9.0`). If no argument was given, ask: "Which version are you documenting?" --- ## Step 1 - Gather context Run these in parallel to understand what shipped: ```bash # Commits since the previous version tag (or last N commits if no tag) git log --oneline --no-merges -50 # Files changed since last tag git diff --stat HEAD~20 # Current ROADMAP.md for feature list cat ROADMAP.md | head -100 ``` Also read: - `release-notes/<previous-version>.md` to understand the format in depth - `CLAUDE.md` for current DB schema version and stack versions - `TODO.md` for features marked done this cycle --- ## Step 2 - Determine file path and status - File: `release-notes/<version>.md` - If the file already exists, read it and extend it - do not overwrite existing content - Status line options: `In Progress`, `Major Release`, `Minor Release`, `Patch Release` --- ## Step 3 - Write the release notes Use this exact structure: ```markdown # v<version> Release Notes **Release Date:** <Month DD, YYYY or "Q? YYYY (planned)"> **Database Schema:** v<N> (frontend IndexedDB) + v<M> (backend PostgreSQL via Flyway) **Status:** <In Progress | Major Release | Minor Release | Patch Release> --- ## Overview <2-4 sentences describing the main themes of this release. Name the milestone codes (e.g. B5, M1) if applicable.> --- ## <Feature Group Name> (<Mi