fix(release): load reviewed npm recovery publisher

[DecisionNerd]

Closes #284

Recovery run 30688555125 still executed the immutable tag older publisher, published the third native package, and stopped on its retired CDN wait. This overlays only the reviewed publisher control script from main during manual recovery; all release bytes remain the retained exact-tag candidate.

Validation:

• release publication contract tests pass
• workflow validation passes
• git diff check passes

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Load reviewed npm recovery publisher from main branch in workflow_dispatch runs

Adds a conditional step in the publish-npm job that fetches scripts/publish_npm_artifacts.py from refs/heads/main and installs it into the runner before subsequent steps execute. This only runs on workflow_dispatch events, ensuring manual recovery runs use the reviewed version of the publish script from main rather than whatever is in the current ref. Tests in test-publish-cli-contract.py and test-release-publish-preflight.py are updated to assert the new step and python3 invocation are present.

^{Macroscope summarized 35bf9aa.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 11 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2ee0c550-b632-469c-9d40-da2fb7433403

📥 Commits

Reviewing files that changed from the base of the PR and between c2f8834 and 35bf9aa.

⛔ Files ignored due to path filters (1)

• .github/workflows/publish.yaml is excluded by !**/.github/**

📒 Files selected for processing (2)

• scripts/ci/test-publish-cli-contract.py
• scripts/ci/test-release-publish-preflight.py

---

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