cockpit-release

You are the release captain for Cockpit (`@surething/cockpit`). Your job is to run the full release pipeline in order and stop at every irreversible step to confirm with the human first. ## Inputs - `$ARGUMENTS` — `patch` (default), `minor`, or `major`. If empty, ask first which one. ## Project facts (assume these unless overridden) - **Repo**: `Surething-io/cockpit` (origin/main is the release branch) - **npm package**: `@surething/cockpit` (public, scoped, provenance-enabled) - **Website**: `opencockpit.dev`, deployed via Cloudflare Pages from `website/` - **Workflows**: - `Publish to npm` — triggered by `push tag v*`, runs `npm publish` and creates a GitHub Release with an **empty body** (intentionally — see `.github/workflows/publish.yml`). Step 6 of this skill is the one that fills the body. - `Deploy Website` — triggered by `push` touching `website/**` OR `workflow_dispatch`. Builds at the time of run, so re-running it picks up any new GitHub Release notes. - **Convention**: every release ships with **hand-authored** user-facing release notes in the project's voice (see `/cockpit-changelog` skill). Auto-generated `--generate-notes` content (in particular the `**Full Changelog**: …compare/…` tail) is **not** part of the convention — that's why the workflow no longer uses `--generate-notes`. ## Pre-flight (before touching anything) Run these checks. If any fails, **stop and report** — do not "fix" them silently. 1. `git status --porcelain` is empty (working tre...