release

# release — bump + push, CI does the tagging Your job: cut a release safely. [RELEASING.md](../../../RELEASING.md) is the authoritative runbook — if it contradicts this skill, it wins. Be terse; surface only failures + final status. ## Phases 1. **Preflight** — clean tree, green smoke: ```bash git status --porcelain # must be empty npm run typecheck ``` For engine changes since the last tag, run the `verify` skill (fixture e2e) before releasing. 2. **Bump** (version lives in one place — package.json): ```bash npm version patch --no-git-tag-version # or minor / major git commit -asm "release: v$(node -p "require('./package.json').version")" ``` 3. **Push** — this is the ship step: once CI sees the version bump on main, the release goes out. Make sure the user actually wants a release cut (a routine end-of-session push must NOT include a version bump): ```bash git push origin main ``` 4. **Watch CI do the rest** — `release.yml` creates `vX.Y.Z`, moves `stable`, publishes the Release (only when the version actually changed): ```bash gh run watch --exit-status "$(gh run list --workflow=release.yml -L1 --json databaseId -q '.[0].databaseId')" gh release view "v$(node -p "require('./package.json').version")" ``` 5. **Manual fallback** (CI unavailable) — from RELEASING.md: ```bash v=vX.Y.Z git tag -a "$v" -m "$v" && git push origin "$v" git tag -f stable && git push -f origin stable gh releas...