fix(security): bump ruint past RUSTSEC-2026-0220 + update ploy tape config pins

[proerror77]

Change contract

Two mutually-blocking fixes combined (each PR's full-CI lane failed on the other's missing half):

1. prediction-markets lockfile: ruint 1.19.0 → 1.20.0 (RUSTSEC-2026-0220 fix release; PR fix(security): update ruint past RUSTSEC-2026-0220 #522 only fixed the main workspace lock).
2. workspace_runtime_retirement config pins updated to post-feat(collector): accept Binance reference kinds on Polymarket market tape #550/feat(deploy): tick-level Polymarket tape recording + faster trade backfill #548 tape reality (Binance kinds + quote_sample_ms=0) — content of test(ploy): update tape config pins for Binance kinds and tick-level sampling #560, cherry-picked here.

Out of scope

• Unmaintained-crate warnings (do not fail the job)
• Scope-gating hole itself (ci: scope path-gating lets cross-lane value pins break main (deployment files pinned by test suites) #563)

Dependency / merge order

Supersedes #560 (closed in favor of this PR). Merge first — the rest of the queue is behind it.

Focused validation

• cargo check -p ploy --locked green
• cargo test -p ploy --test workspace_runtime_retirement: 18 passed, 0 failed

Rollout / rollback impact

Lockfile + test pins only. Rollback = revert.

Issue relationship

Closes #561

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 7 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: fe935988-996e-49df-9a5e-fa3a4c01093d

📥 Commits

Reviewing files that changed from the base of the PR and between ef29c05 and 779f85e.

⛔ Files ignored due to path filters (1)

• rust_hft/prediction-markets/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• rust_hft/prediction-markets/config/research_missions/polymarket-btc-5m.example.json
• rust_hft/prediction-markets/config/research_missions/polymarket-sol-5m.example.json
• rust_hft/prediction-markets/crates/ploy-research/prediction-policy-dependencies.linux.sha256
• rust_hft/prediction-markets/crates/ploy-research/prediction-policy-dependencies.linux.txt
• rust_hft/prediction-markets/tests/workspace_runtime_retirement.rs

---

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.}