announce-release-to-customerslisted

# Announce Release to Customers Describe a release that already happened, in words a customer can act on, with each item traceable both backwards to the commit that produced it and forwards to the customer signal it answers. Two failure modes shape this skill. A release note written from a model's impression of a codebase announces work nobody shipped. A release note written only from commit subjects tells customers about refactors they cannot see. The change list is therefore an input, and the translation is the work. ## Inputs Require: - the release reference: a tag, a version, or a commit range; - a change list obtained deterministically, each item carrying its own reference — a commit hash, a merge request, or a CHANGELOG heading; - the artifact directory holding `signals.jsonl` and `decisions.jsonl`, when a run exists to link against; - the intended audience and channel, as a statement of intent only. Obtain the change list by one of three means and record which one was used: ```bash git log --no-merges --pretty=format:'%h %s' <previous-tag>..<release-tag> ``` reading the release section of `CHANGELOG.md`, or accepting a list the person provides. There is no fourth means. If none is available, stop and say so rather than reconstructing the release from the working tree. ## Workflow 1. Record the release reference and how the change list was obtained. 2. Copy each change into `internal_summary` verbatim, keeping the team's own words as the source text a r