Write release notes people will actually read

Shipping a version and the changelog currently says "various improvements".

Write release notes from the changes below, for users rather than for the team.

Rules:
1. Lead with what someone can now do that they could not before. Not the component name, not the ticket number.
2. One entry per user-visible change. Group internal work into a single closing line if it is worth mentioning at all.
3. Plain verbs. No "enhanced", "optimised", "streamlined", "revamped".
4. Where behaviour changed rather than improved, say so clearly and explain what to do differently.
5. Bug fixes described by the symptom the user saw, not by the cause.
6. Keep the whole thing under 250 words.

Then tell me which changes deserve more than a line in the notes, such as an email or an in-product tour.

Changes:

Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.