releaselisted

# Cut a Tandem Release Codifies the release sequence used for v0.14.3 / v0.15.0 / v0.16.0. 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` — FOUR values in one file: the top-level `version`, plus the `tandem-editor@<version>` npx pins in `mcpServers.tandem.args`, `mcpServers.tandem-channel.args`, AND the `experimental.monitors[].command` shell string (`npx -y tandem-editor@<version> monitor` — added #1201; it lives in a `command` string, invisible to the `args`-array walker, so it has its own guard case in `plugin-version-pin.test.ts`. Miss it and the plugin monitor stays pinned to the previous, dormant version) 3. `src-tauri/Cargo.toml` — `[package].version` (the Cowork installer pins its npx spec via `env!("CARGO_PKG_VERSION")`; stale = ships a build pinning the WRONG published npm version) 4. `src-tauri/tauri.conf.json` — `version` (drives desktop artifact names `Tandem_<version>_x64.dmg`, … AND the tauri-action `__VERSION__` that names/targets the GitHub release; stale = installers uploaded onto the PREVIOUS release — this bit v0.15.0, clobbering v0.14.3's published artifa