releaselisted

# /release You are cutting a Pinta release. Follow these steps in order, confirming before each externally-visible action (push, publish, release). Use the existing `scripts/release.mjs` for build/zip/verify — don't reinvent it. Accepts an optional bump kind as argument: `patch`, `minor`, `major`, or `<exact-version>` (e.g. `0.4.0`). If none given, ask the user via AskUserQuestion. ## Pre-flight (always) 1. Check `git status` is clean. If not, stop and tell the user. Don't silently stash. 2. Check `npm whoami` returns `kevzlou7979`. If 401 or wrong user, stop and tell the user to fix `~/.npmrc` (automation token should be live). 3. Check `gh auth status` shows kevzlou7979 logged in. If not, stop. 4. Read current version from `companion/package.json` and `extension/package.json`. They must match. If they drift, stop. Also note `pinta-plugin/.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json` (`plugins[0].version`) — these get bumped in Step 4 and should track the same number. If any pre-flight fails, surface the actual error — don't paper over it. ## Step 1 — Decide the new version Compute the new version based on the bump kind: - `patch`: 0.3.0 → 0.3.1 - `minor`: 0.3.0 → 0.4.0 - `major`: 0.3.0 → 1.0.0 - `<x.y.z>`: use exact If no arg given, AskUserQuestion with all three options + "Other" for explicit version. Recommend patch by default. ## Step 2 — Ask for the release summary AskUserQuestion: "One-line summary for this release?" — g