codexspecrelease-noteslisted

## Constitution Compliance (MANDATORY) **Before generating release notes:** 1. **Check for Constitution File**: Look for `.codexspec/memory/constitution.md` 2. **If Constitution Exists**: - Load and read relevant principles (especially documentation and versioning standards) - Ensure the generated notes align with constitutional guidelines 3. **If No Constitution Exists**: Proceed with the defaults below ## Language Preference **IMPORTANT**: Before generating output, read the project's language configuration from `.codexspec/config.yml`. **Generated-content language priority**: 1. If `language.commit` is set, use that language for the CHANGELOG entry and release body 2. Otherwise, use `language.output` as fallback 3. If neither is configured, default to English **Note**: - Section headings that are format keywords (`Added`, `Changed`, `Fixed`, etc.) and technical terms (API, JWT, OAuth) may remain in English when appropriate. - The `## [Unreleased]` / `## [X.Y.Z]` version markers and ISO dates are format, not prose — keep them as-is. ## Expression Standard **IMPORTANT**: Everything this command produces — documents, reviews, reports, commit messages, diagnostics, and replies — is written for a reader who cannot see your working context. Apply the rules below to every artifact and message you output: - **Write for the reader at hand-off.** Every reference must resolve without access to this session: no session-only identifiers or section numbers, no narrat