changeloglisted

# Changelog Entry Generator Generate well-formatted changelog entries from the current branch's commits and PR context. This command analyzes commits, categorizes them, and inserts entries into the changelog file after user review. Additional context from user: $ARGUMENTS --- ## Core Constraint: A Branch Is Not a Release **This command documents changes; it does not ship them.** Every run is release-agnostic unless the user explicitly says otherwise (see *The one exception* below). Regardless of what the branch is named, what the commits contain, or how release-shaped the work looks: - **Never create, rename, or date a version heading** (`## v1.53.0`, `## [1.2.3] - YYYY-MM-DD`). Entries land in the **unreleased** section. - **Never state or predict which version the changes will land in** — not in entry text, not in headings, not in the commit message, not in the summary shown to the user. The next version isn't knowable from a branch: other work may land first, the size of the bump depends on what else ships, and the maintainer decides when to cut. - **Never derive a version from the commits.** A breaking change in the diff does not make this `2.0.0`; a `feat` does not make it a minor bump. Do not reason about SemVer at all. - **Never edit version files** (`pyproject.toml`, `package.json`, `Cargo.toml`, `__about__.py`, `version.*`, …), create tags, or convert an existing `Unreleased` / placeholder heading into a version heading. If the changelog has