release

# Release ArcKit Drive the ArcKit release flow end to end. This skill is the executable companion to [`docs/RELEASING.md`](../../../docs/RELEASING.md) — that doc is the source of truth; if the two disagree, trust `RELEASING.md` and update this skill. The target version is `$ARGUMENTS` (e.g. `/release 5.10.0`). If no version was given, ask for it before doing anything — never guess a version. <HARD-GATE> This workflow tags and publishes to public GitHub repos. Do NOT run any step that pushes, tags, or publishes without the user confirming the version and that the PR is already merged to `main`. Show the plan and the computed version first, then proceed step by step. </HARD-GATE> ## Preconditions Confirm all of these before touching version files: 1. The feature PR is **merged to `main`** — releases are cut from `main`, never from a branch. 2. Working tree is on `main` and clean: `git checkout main && git pull && git status`. 3. The version `$ARGUMENTS` is valid semver (`X.Y.Z`) and **greater** than the current plugin version (`cat plugins/arckit-claude/VERSION`) and CLI version (`cat VERSION`). 4. `GH_TOKEN` is set in the environment (needed by `push-extensions.sh`). If any precondition fails, stop and surface it. Do not work around it. ## Release flow Run these in order. Each script is idempotent or safe to re-run except the `git tag`/`git push` steps. Pause after step 6 (the commit) and after step 8 before tagging to let the user confirm. ```bash # 1. Edit CHANG...