changelog-authoringlisted

# Changelog Authoring Turn commit messages, project records, or both into concise changelog entries that explain changes to users and operators. Support a pull request, the current branch compared with its base, or an explicit release range. A planning directory is optional. ## Workflow 1. Preserve Git index and working-tree state while gathering evidence. Do not stage, unstage, commit, amend, reset, switch branches, or discard files unless explicitly asked. Exclude uncommitted changes from a commit-based summary. 2. Honor the requested source: commit messages, project records, or both. For a PR or branch request with no specified source, start with its commit messages and use targeted diffs or linked records to clarify consequential claims. 3. Resolve the comparison using the rules below. Record the selected refs and commit SHAs so the evidence has a stable scope. 4. Read the selected evidence using the relevant source guidance below. Do not require planning documents for a commit-based changelog or invent completed implementation from a planning record. 5. Consolidate related changes into product-facing entries. Use diffs to resolve vague messages, duplicate descriptions, fixups, or reverts when that evidence is available. If the request limits evidence to messages, state consequential uncertainty instead of inventing details. 6. Return a draft when requested. When asked to create or update a file, use the requested path or root `CHANGELOG.md` and fo