ci: add workflow_dispatch to Release

[ScriptedAlchemy]

Summary

• Add workflow_dispatch to Release so we can run OIDC + provenance publish without another main push.
• No runner/job/step changes.

Test plan

• Merge, then gh workflow run Release --ref main
• Confirm run starts and uses existing OIDC trusted publishing path

[changeset-bot]

⚠️ No Changeset found

Latest commit: 658931d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-16T23:20:19.726656Z	658931d	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 658931d2df

ℹ️ 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]

Restrict manual releases to the main branch

A write-capable user can now dispatch this workflow with gh workflow run Release --ref <feature-branch>, causing every release step to check out and operate on an unreviewed ref while retaining contents: write and id-token: write. The gh workflow run documentation defines --ref as the branch or tag containing the workflow version, so a feature branch with a modified package version and no pending changesets can reach the OIDC-enabled npm run release path without passing main-branch review. Gate the release job to refs/heads/main or reject non-main dispatches.

Useful? React with 👍 / 👎.