changeloglisted

# Changelog — Release Changelog Maintainer Updates `CHANGELOG.md` at the project root using the [Keep a Changelog](https://keepachangelog.com) format. Run at release time before generating the client report or review checklist. --- ## Steps ### 1. Read existing changelog Check if `CHANGELOG.md` exists at the project root: ```bash ls CHANGELOG.md 2>/dev/null || echo "NOT FOUND" ``` If missing, create it with this header, worded exactly as the spec words it: ```markdown # Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [Unreleased] ``` Do not paraphrase those two sentences. The spec's own wording is the standard across every studio repo. An `[Unreleased]` section sits above the most recent release and collects changes before they are cut into one. ### 2. Find the last release ```bash git tag --sort=-version:refname | head -5 git log $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD --oneline 2>/dev/null || git log --oneline -20 ``` If no tags exist, use all commits. ### 3. Read QA review-passed items ```bash ls qa/qa-review-passed/ 2>/dev/null ``` Read each file for context on what was fixed or verified. ### 4. Read any release notes Check for release notes in: - `.claude/release-notes.md` - `docs/release-notes.md` Use if present — these take p