Fix: clarify release branch check workflow name

[flyingrobots]

Summary

• Rename the visible Release Autotag workflow to Main Push Release Branch Check.
• Rename the visible job to Check merged release branch and make the normal-skip summary explicitly say no release tag was created.
• Update release runbook, release PR preview text, README release blurb, and local preflight output to use the less alarming wording.

Closes #700

Validation

• npm run lint:md -- README.md .github/RELEASE.md
• npm run lint:md:code
• npm run lint:docs-topology
• bash -n scripts/release-preflight.sh
• workflow YAML parse check for .github/workflows/release-autotag.yml and .github/workflows/release-pr.yml
• npm run release:guard -- --stage prep-pr
• pre-push IRONCLAD M9 gate, including stable unit-test shards

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6775f614-9f5c-4ce6-8db5-6c8c4b0a40c7

📥 Commits

Reviewing files that changed from the base of the PR and between f20b919 and a87129b.

📒 Files selected for processing (2)

• .continuum/release.yml
• .github/workflows/main-push-release-branch-check.yml

💤 Files with no reviewable changes (1)

• .github/workflows/main-push-release-branch-check.yml

📜 Recent review details

⏰ Context from checks skipped due to timeout. (5)

• GitHub Check: test-deno
• GitHub Check: coverage-threshold
• GitHub Check: test-node (22)
• GitHub Check: preflight
• GitHub Check: type-firewall-lint

🔇 Additional comments (1)

.continuum/release.yml (1)

50-50: 📐 Maintainability & Code Quality

Rename is isolated; no code in the repo reads workflow.autotag.

			> Likely an incorrect or invalid review comment.

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Clarified release terminology across docs and status messages, replacing “Release Autotag” with “Main Push Release Branch Check.”
  • Updated release instructions to better describe when tags are created and when manual publication is required.
• Chores
  • Renamed related workflow labels and job names for consistency.
  • Improved the no-release-detected summary message shown during checks.

Walkthrough

Renames the Release Autotag workflow to Main Push Release Branch Check across the workflow YAML (name, concurrency group, job id/name, skip summary text), the continuum release config, RELEASE.md, README.md, release-pr.yml PR comment, and release-preflight.sh messaging.

Changes

Workflow rename and doc updates

Layer / File(s)	Summary
Workflow YAML and continuum config rename .github/workflows/main-push-release-branch-check.yml, .continuum/release.yml	Workflow display name changed to "Main Push Release Branch Check", concurrency group and job id/name updated accordingly, skip-summary message made explicit; continuum config now points to main-push-release-branch-check.yml.
Docs, runbook, PR comment, and preflight script .github/RELEASE.md, .github/workflows/release-pr.yml, README.md, scripts/release-preflight.sh	All operator-facing references to "Release Autotag" / "autotag" replaced with "Main Push Release Branch Check" / "main-push release branch check".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• git-stunts/git-warp#675: Introduced the Release Autotag workflow and the release-pr.yml wording that this PR renames.
• git-stunts/git-warp#678: Updated autotag/manual-registry behavior and messaging in the same files (RELEASE.md, release-pr.yml, release-preflight.sh) now being renamed.
• git-stunts/git-warp#687: Modified .continuum/release.yml and release-preflight.sh messaging at the same touch points updated here.

Poem

🐇 A workflow once called "Autotag"
was causing quite a scare —
each ordinary merge to main
looked like a release affair!
Now "Branch Check" names the game,
and all is calm out there. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the workflow naming clarification.
Description check	✅ Passed	The description includes a summary, issue reference, and validation details, so it is mostly complete despite missing ADR checkboxes.
Linked Issues check	✅ Passed	The PR matches #700 by renaming the workflow, updating skip messaging, and keeping tag/publish behavior unchanged.
Out of Scope Changes check	✅ Passed	The changes stay focused on release workflow naming and related operator-facing text with no clear unrelated additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Release Preflight

• package version: 18.1.2
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If this PR is from a release/* branch and merges to main, Main Push Release Branch Check will run final preflight and create v18.1.2. A maintainer who is a JSR @git-stunts scope member must then dispatch the Release workflow manually.

[flyingrobots]

Code Lawyer Self-Audit Finding

@codex please confirm the naming cleanup after this follow-up commit.

Severity	Source	File / lines	Issue	Mitigation prompt
P4	Self	.continuum/release.yml:49-51 and .github/workflows/release-autotag.yml	The PR renamed the visible workflow, but the release profile and workflow filename still carried the old autotag noun, leaving release automation source truth partially stale.	Rename the release-profile workflow key and workflow file to main_push_release_branch_check / main-push-release-branch-check.yml, then rerun workflow YAML parsing, release-profile tests, Markdown gates, and release guard.

[github-actions]

Release Preflight

• package version: 18.1.2
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If this PR is from a release/* branch and merges to main, Main Push Release Branch Check will run final preflight and create v18.1.2. A maintainer who is a JSR @git-stunts scope member must then dispatch the Release workflow manually.

[flyingrobots]

Code Lawyer Activity Summary

@codex confirm: this pass found one stale naming source-truth issue, resolved it, and rechecked the PR.

Item	Severity	Source	File	Commit	Outcome
Remove stale autotag release-profile/workflow filename noun	P4	Self	.continuum/release.yml, .github/workflows/main-push-release-branch-check.yml	a87129b3	Fixed: release profile now uses main_push_release_branch_check; workflow file renamed to main-push-release-branch-check.yml; stale-name scan is clean.

Validation:

Gate	Result
Phase 0 clean worktree	Passed
git fetch origin --tags	Passed
GraphQL review-thread sweep	Passed: 0 unresolved/open threads
git diff --check	Passed
Workflow/release profile YAML parse	Passed
bash -n scripts/release-preflight.sh	Passed
npm run lint:md -- README.md .github/RELEASE.md	Passed
npm run lint:md:code	Passed
npx vitest run test/unit/scripts/release-profile.test.ts	Passed: 3/3
npm run lint:docs-topology	Passed
npm run release:guard -- --stage prep-pr	Passed
Pre-push IRONCLAD M9	Passed
GitHub PR checks	Passed
CodeRabbit	Passed

Merge gate: open from this audit perspective.