Wire-compatible with X.Y.x — existing pairings and clients keep working. <one sentence on how
older/newer clients negotiate or fall back, so nobody fears updating.>

<Optional: one or two sentences naming the headline change of this release — this whole lead-in
(everything above the first `##`) is what the Discord #releases embed shows, so make it read as a
standalone summary.>

## TL;DR

- **<The one thing you would tell someone in a sentence.>**
- **<Second. Anything that needs the reader to ACT goes here too, and in `## Before you update`.>**
- **<Third. Three to six bullets, one line each. This is what a reader sees instead of giving up.>**

## Before you update

<DELETE THIS SECTION if nothing in the release needs the reader to do anything. Otherwise: one
bullet per action, saying plainly what breaks if they skip it.>

## New

- **<Lead-in>.** <What changed and why it matters, concretely. Which side to update.>

## Improved

- **<Lead-in>.** <…>

## Fixed

- **<Lead-in>.** <…>

## For developers

Protocol, ABI, driver and embedder detail — including the version table and any breaking
changes — is in [CHANGELOG.md](https://git.unom.io/unom/punktfunk/src/tag/vX.Y.Z/CHANGELOG.md).

<One sentence if and only if there is a breaking change an embedder must act on, so it is not
missed by someone who does not follow the link.>