changeloglisted

# Changelog A changelog is a curated, human-readable record of notable changes to a project. It exists for users and consumers of the project — not for developers. Every entry should answer: "How does this affect me?" This methodology follows [Keep a Changelog](https://keepachangelog.com) conventions. Write the prose this skill governs at a seventh-grade reading level, in STE-flavored mode — short sentences, common words, no unexplained jargon. Full methodology: `writing-prose`. Before you finalize prose this skill governs, call the Skill tool with `writing-prose` and apply its `## Self-lint` checklist. ## File Structure The changelog lives at `CHANGELOG.md` in the project root. If it does not exist, create 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/). ## [Unreleased] ### Added - ... ### Changed - ... ### Fixed - ... ``` ## Section Types Every entry belongs to exactly one section: | Section | When to use | |---------|-------------| | `Added` | New features, new commands, new options | | `Changed` | Changes to existing behavior that users will notice | | `Deprecated` | Features scheduled for removal in a future release | | `Removed` | Features removed in this release | | `Fixed` | Bug fixes | | `Security` | Vulnerability fixes — always document these | ## The Unreleased Section All changes go under `[Unreleased]` until a version i