release-noteslisted

# Release Notes ## Core Question What user-facing release-note text is supported by the available evidence, and what limitations must be disclosed? ## When To Use Use this skill when the user asks to: - draft release notes, - summarize changes for a release, - turn changelog entries into a release announcement, - draft a GitHub release body as text, - identify highlights, fixes, breaking changes, migrations, deprecations, or known issues, - locally update a release-note file when explicitly requested. ## When Not To Use Do not use this skill to create Git tags, publish hosted releases, call release APIs, push files, change versions, or edit changelog structure. Route to: - `tag-release` for Git tag creation. - a future `publish-release` skill or manual workflow for hosted release publication. - `version-bump` for version changes. - `changelog-maintenance` for changelog file maintenance. - `conventional-commits` for commit message work. ## Required Evidence Inspect or establish: - release range or previous/current tag, - changelog entries, - commit log and PR/issue references when available, - version number and release date when provided or evidenced, - breaking changes and migration notes, - security/performance evidence before claiming those categories, - known issues only when evidenced, - target audience and output format when relevant. ## Operating Contract This skill drafts or locally updates release-note text only. It does not create Git tags, publish hos