ci(rust): move market-recorder release suite back to the sccache-warm job

[proerror77]

Change contract

Move test-polymarket-market-recorder-release.sh out of Rust Fast Gates into the sccache-warm heavy job (as its own gated step, identical env/invocation). Fast Gates returns to pure checks (layout / Python-ban / fmt / bash -n / shellcheck / fixture-only suites).

Evidence

Measured on run 30684861791 (first warm run after #559): Fast Gates 5m20s total, of which the market-recorder suite was ~4.5min (04:58:36→05:03:08) because it compiles recorder artifacts without sccache warmth. Target in #558 is ≤3min; the remaining suites sum to well under it.

sccache meanwhile is working: heavy Rust Workspace went 17m44s (pre-#559) → 10m12s with 46.4% hit rate on the first warm run. cache_write_errors: 253 investigated: GHA-backend write contention (per-artifact PUT races), zero read errors, zero cache errors, build unaffected — benign upstream behavior, monitoring rather than restructuring.

Out of scope

• cache_write_errors fix (upstream contention, benign)
• test-polymarket-raw-ops-control-plane.sh (already in the heavy job)

Dependency / merge order

Stacks on #559 (merged). No other interaction.

Focused validation

• .github/scripts/test-select-rust-ci-scope.sh PASS
• ci.yml YAML parse OK; the moved step is byte-identical invocation

Rollout / rollback impact

CI-only. Rollback = revert.

Issue relationship

Refs #558

[coderabbitai]

Warning

Review limit reached

@proerror77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e8f2a9d7-5eb6-4889-92c2-0628225508d5

📥 Commits

Reviewing files that changed from the base of the PR and between 837a579 and ab309c9.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c119a6b01

ℹ️ 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".