fix(release): gate version bumps to deliverable-impact commits

[iamfj]

What does this PR do?

Tightens release automation so package versions advance only for deliverable-impact commits, and promotion PR automation runs only when an actual prerelease is published.

Type of change

• Bug fix
• New feature
• Refactor (no behavior change)
• Documentation
• Tests
• Build / CI

Checklist

• npm run check:ci passes (lint + format)
• npx tsc --noEmit passes (type check)
• npm test passes (unit tests)
• New code has tests (happy path + primary error case)
• Commit messages follow Conventional Commits

Testing

npm run check:ci
npx tsc --noEmit
npm test

Notes for reviewers

• .releaserc.cjs: adds explicit releaseRules to prevent bumps for non-deliverable commit types (refactor, chore, ci, docs, style, test, build) and to suppress infra scopes (ci, release, workflow) even if commit type is releasable.
• .github/workflows/release-promote-next-to-main.yml: removes push trigger so promotion PR upsert runs on release.published (or manual dispatch), reducing PR churn from non-releasable commits.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3744496dd8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[iamfj]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a54ad225f3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Apply scope exclusions before breaking-change classification

classify_commit returns releasable immediately when it sees ! or BREAKING CHANGE, so a commit like fix(ci)!: ... is categorized as releasable and listed under “Ships in stable.” In .releaserc.cjs, scope: ci|release|workflow is explicitly release: false, so those commits should be no-version-impact even when breaking. This makes the promotion PR metadata diverge from semantic-release behavior and can mislead release decisions.

Useful? React with 👍 / 👎.