imprnt-releaselisted

# imprnt release skill Promote a **stable** release to npm `latest`. (Edge auto-publishes on every push to master, so you never touch that here.) For how the whole pipeline works (channels, versioning, OIDC, the gate), read [`site/docs/contributing.md`](../../../site/docs/contributing.md). This skill only drives the stable cut, so that architecture lives in one place and can't go stale here. ## THE ONE RULE: no prose by default **Default = ship. No articles, no blog drafts, no release-note essays.** The GitHub Release gets the minimal auto-notes the workflow generates, and that's it. Unprompted prose is the single most common frustration with release commands, so only write it on an explicit `--article`. - `imprnt-release` → preflight, show the plan, fire the gated workflow, report. Silent on prose. - `imprnt-release --dry-run` → plan only, publishes nothing. - `imprnt-release status` → show what's on `latest` vs `edge`. - `imprnt-release --article` → see the section at the end. Opt-in only. ## Steps Run from the imprnt repo root. Find it, don't assume a path. 1. **Preflight.** The workflow releases from origin/master, so confirm local is clean and pushed: ```sh git branch --show-current # must be master git status --porcelain # must be empty git fetch origin --tags --quiet git rev-parse HEAD; git rev-parse origin/master # must match, push first if not ``` If master is dirty or behind origin, stop and tell the user. Don't