electron-release

# Release Electron Build Release the reviewed repository changes as the next patch version. This workflow changes version files, creates a commit, pushes it, and creates a public GitHub release, so keep every step scoped and verifiable. ## Safety Rules - Treat explicit invocation or a direct release request as authorization for this release sequence, not for unrelated local files. - Inspect the worktree before changing it. Preserve unrelated edits and never use `git add -A` or `git add .`. - Exclude local-only state such as `.codex/audit/`, root-level generated bundles, screenshots, caches, credentials, and environment files. - Stop for user direction when a dirty file's inclusion is ambiguous or the current branch, remote, or release target is unexpected. - Never delete or overwrite a remote release, tag, or pushed commit as automatic error recovery. ## 1. Preflight 1. Resolve the Git root and read the applicable `AGENTS.md` and `CLAUDE.md`. 2. Inspect `git status --short`, the complete relevant diff, the current branch, its upstream, and the configured GitHub remote. 3. Classify every changed and untracked file as release content, required version metadata, generated artifact, or unrelated local state. Record the exact paths intended for the commit. 4. Verify GitHub CLI authentication with `gh auth status`. 5. Refresh tags from the release remote and query the latest published release with `gh release list`. Do not rely only on potentially stale l...