releaselisted

# Cut a Tandem Release Codifies the release sequence used from v0.14.3 onward, and refined by every cut through v0.22.0 — including the global-install upgrade step, the two changelog gaps, the rebuild-before-retest step, and the duplicate-draft race described below. The version bump has **SIX surfaces**, none of which bump automatically. Surfaces 1–4 are CI-guarded by `tests/plugin/plugin-version-pin.test.ts` (any divergence from `package.json` fails CI); surfaces 5–6 are **not guarded** — this skill is what prevents them drifting. ## The six version surfaces 1. `package.json` — `version` (the reference value the CI guard compares against) 2. `.claude-plugin/plugin.json` — **FIVE** values in one file: the top-level `version`, plus the `tandem-editor@<version>` npx pins in `mcpServers.tandem.args`, `mcpServers.tandem-channel.args`, AND **one per entry** in `experimental.monitors[].command` (`npx -y tandem-editor@<version> monitor` — added #1201; #1354 made it two entries, because the arm trigger has to be declared under both the qualified and the bare skill name. Each lives in a `command` string, invisible to the `args`-array walker, so they have their own guard case in `plugin-version-pin.test.ts`, which loops every entry. Miss one and that monitor stays pinned to the previous, dormant version.) **Count the entries, do not trust this number** — it was already stale once, when the second monitor was added. 3. `src-tauri/Cargo.toml` — `[packa