changeloglisted

# Generate Changelog Entry Generate a formatted CHANGELOG entry from commits since the last release tag. ## Steps 1. Find the last release tag: ```bash git describe --tags --abbrev=0 ``` 2. List commits since that tag: ```bash git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges ``` 3. **Read the diff of each change, not its subject line.** `git show <sha> -- <path>` for anything you are about to describe. The commit prefix tells you where an entry goes; only the diff tells you what it says. v0.20.0 shipped five defective entries composed from PR titles — the worst promised a detection capability that did not exist. Where a change landed across several commits (a fix, then its review corrections), describe the **final** state: `git log --oneline v<prev>..HEAD -- <path>` shows whether what you just read was later amended, and `git show v<prev>:<file>` settles "is this actually new?" 4. Group into Keep a Changelog categories based on conventional commit prefixes: - `feat(...)` → **Added** (new features) or **Changed** (enhancements to existing) - `fix(...)` → **Fixed** - `refactor(...)` → **Changed** - `docs(...)` → **Documentation** - `test(...)` → **Tests** - `chore(...)` → **Maintenance** - `perf(...)` → **Performance** - Security-related commits → **Security** 5. **Open the version with a plain-language summary, before any `###` subsection.** Two or three sentences for someone who does not know the codebas