release-versionlisted

Deploy or cut a versioned release of Agentmaster — the local deploy inner-loop (close → build → relaunch) AND the public GitHub release pipeline (tag or dispatch release.yml → monitor → verify the 4 signed assets → apply notes → publish). Encodes the hard rules: hold the build mutex, pin `-R Nucs/Agentmaster` (gh defaults to the upstream microsoft/terminal remote), confirm the version with the user first, build the RELEASE identity, and ALWAYS pre-validate with a clean local Release build (incremental Debug builds mask clean-build errors the runner WILL hit). Use when the user asks to release a new version, cut/publish a release, ship vX.Y.Z, cut a NIGHTLY (vX.Y.Z-prerelease-nightly — auto-marked prerelease, offered only to nightly-opted users), or deploy the dev instance.
Nucs/Agentmaster · ★ 1 · Code & Development · score 77

Install: claude install-skill Nucs/Agentmaster

# Agentmaster — deploy & release a version Two distinct workflows. **Path A (local deploy)** = the inner loop that gets your code into the running dev instance (standing-authorized, no prompt). **Path B (public release)** = cut a versioned GitHub Release (outward-facing — confirm the version with the user FIRST, never self-initiate). They share the same pre-flight. The authoritative source is **`CLAUDE.md`** → *Deploy & run*, *Concurrency lock*, and *Releasing a public version*. This skill is the runnable checklist; if it ever disagrees with CLAUDE.md, CLAUDE.md wins — re-read it (it changes). For the LOCAL machine's build flavors, the production (Release-layout) install, the self-kill check before closing an instance, and the build/registration troubleshooting matrix (PRI210, 0x80070020 re-register collisions, stale mutex), see the **`build-install`** skill — it owns the local how; this skill owns the release pipeline. NOTE: Path B's pre-validation build (B1) relinks the PRODUCTION instance's Release layout in place — close production first (path filter `'*\bin\x64\Release\*'`), and re-stamp the layout version afterwards if you re-register it (build-install §4). --- ## Hard rules (both paths) 1. **Hold the `build-launch` mutex** around any full-exe build, launch, deploy, or closing our instance. (A lib-only compile-check does NOT need it.) It's a filesystem lock shared by all agents — persists across separate Bash calls. ```bash TOKEN=$(bash tools/am-lock.s