releaselisted

# Release Bump version, tag, push, create a GitHub release with auto-generated notes, and present npm publish command. Supports both stable releases and release candidates (RC). ## Inputs - `$ARGUMENTS` — target version (e.g. `1.15.0`), `rc` for release candidate, or empty for auto-detection. ## Release Type Detection Determine release type from `$ARGUMENTS` and current branch: - If `$ARGUMENTS` contains `rc`, or current branch is not `main`/`master` → **RC release** - If `$ARGUMENTS` is a version like `1.15.0-rc.1` → **RC release** with that exact version - Otherwise → **Stable release** ## Workflow ### Step 1: Verify Clean Working Tree Run `git status --short`. If there are uncommitted changes, warn the user and **stop**. ### Step 2: Determine Branch & Release Type ```bash git branch --show-current ``` - **Stable release**: must be on `main` or `master`. If not, warn and ask to confirm or switch to RC. - **RC release**: can ship from any branch. ### Step 3: Determine Version Read current version from `package.json`. If `$ARGUMENTS` is an exact version, use it directly. **For stable releases:** Analyze commits since the last stable tag (exclude RC tags) to suggest a bump type: - **major** — breaking changes - **minor** — new features (feat commits) - **patch** — bug fixes, chores, docs only Present the suggested bump type and resulting version to the user using `AskUserQuestion` with options: patch, minor, major (put the recommended one first with "(Recommend