# Changelog Policy
The repository changelog lives at `CHANGELOG.md` and follows Keep a Changelog 1.1.0. Use the standard buckets: `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, and `Security`.
Add user-visible changes to `## [Unreleased]` as part of normal feature and fix work. Keep entries deterministic, concise, and human-scannable. Contributor-only repository maintenance can be recorded when it changes how maintainers work, such as reorganizing docs or automation entrypoints.
Treat published version sections as immutable historical release records. Do not rewrite old shipped sections merely because current commands or paths changed. If a factual correction is needed after release, record it in `Unreleased` or a later release instead of editing old history. History is allowed to be inconvenient; this is one of its few talents.
During release prep, move finalized `Unreleased` entries into `## [X.Y.Z] - YYYY-MM-DD`, create a fresh empty `Unreleased` section, and update comparison links at the bottom. GitHub Release notes are published from the matching version section in `CHANGELOG.md`; do not rely on autogenerated GitHub notes.