ci: Binding RC Linux lanes consume Bazel-built natives

[DecisionNerd]

Summary

• Linux Binding RC Python + Node x64 build Bazel cdylibs and assemble via binding_rc_bazel_native.py / assemble_bazel_binding_packages.py
• Stop maturin/napi recompile on those lanes; drop their Cargo target/ sticky mounts
• release_candidate emits index.js/index.d.ts from a retained Linux addon (emit-node-loaders) instead of napi build
• Update bazel-migration-cutover.md; keep macOS/Windows/cross napi-maturin as follow-on

Test plan

• python3 scripts/ci/test-binding-release-candidate.py
• python3 scripts/ci/test-ci-storage-policy.py
• python3 scripts/ci/test-assemble-bazel-binding-packages.py
• CI Gate green on exact head
• Binding RC dispatch smoke on a non-prod SHA (optional)

Closes #450

Made with Cursor

---

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

Note

Switch Linux RC lanes to consume Bazel-built native binaries

• Linux Python RC builds now assemble the abi3 wheel from Bazel outputs via the new binding_rc_bazel_native.py script instead of invoking maturin; macOS and Windows remain on maturin.
• Linux Node x86_64 RC builds now stage the .node addon and loaders via Bazel instead of napi; other platforms remain on napi/napi-cross.
• The release assembly job emits Node loaders via emit-node-loaders from the retained Linux addon rather than recompiling with napi build.
• Cargo registry caching, sticky-disk mounts, and rustc-wrapper setup are skipped on Bazel lanes and retained only for maturin/napi lanes.
• CI policy tests in test-binding-release-candidate.py are updated to enforce presence of Bazel build paths and absence of recompiling napi build in release assembly.

^{Macroscope summarized ecda605.}

[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: 30 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: 4d1ff6a7-59f5-4659-a36b-96b203c5aee0

📥 Commits

Reviewing files that changed from the base of the PR and between 02fa574 and ecda605.

⛔ Files ignored due to path filters (2)

• .github/workflows/binding-release-candidate.yml is excluded by !**/.github/**
• docs/development/bazel-migration-cutover.md is excluded by !**/*.md, !**/docs/**

📒 Files selected for processing (2)

• scripts/ci/binding_rc_bazel_native.py
• scripts/ci/test-binding-release-candidate.py

---

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