session-releaselisted

# Session Release Orchestrate a full release cycle: version bump, artifact packaging, and satellite content verification. Open with one sentence saying what you are about to do and what it will produce. ## Non-Negotiables 1. **Never auto-run builds.** Builds often require signing keys, CI pipelines, or Windows/macOS-specific environments. Print the command and wait for the user. 2. **Never modify lock files manually.** Lock files (`package-lock.json`, `Cargo.lock`, `pnpm-lock.yaml`) are regenerated by the toolchain. Hand-editing corrupts them. 3. **User approves at both gates.** Step 3 (build) and Step 6 (satellite updates) require explicit user confirmation, or a standing policy that already covers exactly that action. No proceeding on silence. 4. **Final version grep must be clean.** Before commit, grep the repo for the old version — nothing should remain except in `CHANGELOG.md`, lock files, and historical references. 5. **Never skip the satellite scan.** The whole point of this skill is to catch the docs site, marketing page, and download modal that still say the old version. 6. **Never accept a verification verdict without comparing its recorded commit range against the candidate revision.** A PASS is evidence about the revision it was recorded against. When they differ, the user decides reuse or rerun explicitly. 7. **Each release action is authorized on its own.** Bumping, packaging, and committing are this skill's work. Tagging, pushing, publishing, deploying, and