release-codevisorlisted

# Release Codevisor Stable is a promotion, never a rebuild. The `Alpha` workflow creates the only signed and notarized app/server artifact set for a commit. `Publish Alpha` publishes those bytes to the Alpha Sparkle channel. `Release` attaches the same bytes to the Stable tag, advances the Stable Sparkle and Linux manifests, updates Homebrew, and attaches a versioned Chrome extension package. Chrome Web Store publication is a separate, explicit workflow and must not run as part of an app release. Do not create, move, or push a version tag manually. The workflow owns the tag. ## Prepare Require a clean release scope and current remote state: ```sh git status --short git fetch origin main --tags main_sha="$(git rev-parse origin/main)" gh run list --workflow release-candidate.yml --commit "$main_sha" --status success --limit 5 ``` Inspect the successful run's `codevisor-release-provenance` artifact. It must say `channel: alpha`, use `main_sha`, and contain the numeric version and build number. Also require a published `vVERSION-alpha.BUILD` prerelease for that provenance. If the Alpha publisher has not run, dispatch `publish-release-candidate.yml` and monitor it first. Generate the prospective Stable notes locally: ```sh node scripts/release/generate-release-notes.mjs \ --channel stable \ --version VERSION \ --commit "$main_sha" \ --output /tmp/codevisor-release-notes.md ``` Read the notes. Every non-merge commit since the previous Stable tag must appear exactly