release

# Release Rove Autonomous release driver for `@sma1lboy/rove`. This is the supervised loop the manual flow in [`docs/RELEASING.md`](../../../docs/RELEASING.md) describes — read that doc once if anything here is ambiguous; it is the source of truth and this skill must never contradict it. > **Releases are automatic** (`.github/workflows/changesets.yml`, since > 2026-08-12): any push to `main` carrying pending changesets triggers the > full chain in Actions — CI-green wait → version+commit → tag → publish. > When the user asks to release, FIRST check whether that workflow already > has it: `gh run list --workflow=changesets.yml --limit 3`. If a run is > mid-flight or completed for the relevant push, jump to Step 4 (watch the > publish pipeline / verify npm). Run the `scripts/release.sh` flow below > only when the automatic path is unavailable (Actions down) or the user > explicitly asks for the local flow — and never while a changesets.yml > run is mid-flight on the same version (they'd race to tag it). The job is: **detect the bump → gate → bump/tag/push → watch CI → confirm published, or stop with a precise report.** Do the whole chain without hand-holding, but stop and surface (never guess) at the two human-judgment gates marked **⚠ ASK** below. ## Hard rules (non-negotiable) - **Never force-push.** No `git push -f`, no `--force-with-lease`, no `git reset --hard` on a shared branch, no retag-over-existing. If a tag or push conflicts, stop and report — recovery is th...