release

## Start Announce: **"Preparing a paad release…"** Read @CLAUDE.md. `make release` and `make tag` own everything mechanical: the promotion of `preview/paad` into `plugins/paad`, the changelog roll, the version rewrite across every manifest and announce line in both trees, the export regeneration, the full check suite, and the annotated tag. This skill owns the parts a Makefile cannot decide — which number to bump to, whether a release is wanted at all, and whether the thing users install actually works afterwards. **Never hand-edit `plugin.json`, `marketplace.json`, `package.json`, a SKILL.md announce line, or the changelog's version headings and link refs.** Those are generated. If the generated result is wrong, fix the generator. **Never hand-edit `plugins/paad` at all.** It is written only by promotion. A hand edit there does not survive: `make release` opens with `make promote`, whose `rsync -a --delete` copies the pre-fix `preview/paad` straight over it. Nothing catches that — the tree is committed so the dirty guard passes, and the result is self-consistent so every check passes. The release ships and the changelog announces a fix that is not in it. Fixes go in `preview/paad`, hotfixes included. ```dot digraph release { "Read [Unreleased]" [shape=box]; "Anything there?" [shape=diamond]; "STOP — ask whether a release is wanted" [shape=box, style=bold]; "Entries within the length rule?" [shape=diamond]; "STOP — trim first, as its own commit" [sha...