release

# Release Skill Cut a new JobPilot release. Host and plugin share **one version** and ship from **one tag** (`vX.Y.Z`), which triggers `.github/workflows/release.yml` - it builds the terminal binaries for all RIDs, publishes the GitHub Release (the terminal archives, which bundle the plugin tree), and syncs the plugin tree into the `claude-plugins` and `codex-plugins` marketplaces. ## Usage The user provides a version (e.g. `2.1.0`) or a bump type (`major`, `minor`, `patch`). With no argument, default to a `patch` bump. ## Context - **Version source of truth (must stay in lockstep):** - `apps/terminal/JobPilot.Terminal.csproj` - the `<Version>` element - `plugin/.claude-plugin/plugin.json` - `"version"` - `plugin/.codex-plugin/plugin.json` - `"version"` - `package.json` - `"version"` - **Tag format:** `vX.Y.Z` (matches the `v*` trigger in `release.yml`). - **Changelog:** `CHANGELOG.md` at the repo root, [Keep a Changelog](https://keepachangelog.com) format, newest release first. The workflow also sets `generate_release_notes: true` for the GitHub Release. ## Steps 1. **Determine the new version:** - Read the current version from all four files above. - If they differ, report the mismatch and reconcile to the highest before bumping. - Use the user's explicit version, else compute from the bump type, else bump patch. - Verify the new version is strictly greater than the current highest. 2. **Pre-flight checks** (stop and report on any failure - d...