releaselisted

# Release Workflow This skill covers the full release lifecycle. Detect the current stage and proceed accordingly. ## Stage detection Check these conditions in order to determine where the user is: 1. **No release branch exists** → Stage 1 (Prep) 2. **On a `release/*` branch, `.tmp/release-context/` exists, `CHANGELOG.md` has only `[Unreleased]`** → Stage 2 (Generate notes) 3. **On a `release/*` branch, `CHANGELOG.md` has the version section** → Stage 3 (Review and PR) 4. **On `main`, `CHANGELOG.md` has the version section, no tag exists** → Stage 4 (Tag and push) 5. **Tag already exists** → Done To check: - Current branch: run `git branch --show-current` - Release context exists: check for `.tmp/release-context/release-context.md` - CHANGELOG has version: look for `## [X.Y.Z]` in `CHANGELOG.md` - Tag exists: run `git tag -l vX.Y.Z` ## Stage 1: Prep Prerequisites: on `main`, clean working directory. If not met, tell the user what to fix. If the user hasn't specified a version, ask them. Run: ``` make release-prep VERSION=vX.Y.Z ``` This creates branch `release/vX.Y.Z` and generates `.tmp/release-context/`. Proceed to Stage 2. ## Stage 2: Generate release notes Read `.tmp/release-context/release-context.md`. Note the version, commit log, and diffstat. **Read detail diffs selectively** based on the diffstat. The summary table shows which files have content and whether they contain a full diff or a diffstat summary: - If `api/v1alpha1/` files appear → read `api-t