CEX: collect complete official USD-M reference batches

[proerror77]

Part of #222.

Change contract

Collect one fail-closed, complete Binance USD-M reference batch from the exact official https://fapi.binance.com origin using serverTime, exchangeInfo, bulk premiumIndex, and bounded per-symbol openInterest requests, preserving source/received clocks and source origin.

Out of scope

Artifact publication/readback, CLI, systemd/deployment/shadow gate/cutover, issues #223/#224, snapshot, evaluator, and research logic.

Dependency or merge order

Depends on PRs #251 and #252 (merged). Merge before the separate artifact publisher/verifier PR, then the CLI PR, then deployment gate. This PR does not close #222.

Focused validation

• TDD red proof: focused tests initially failed because the reference source, timed JSON, complete collector, and official-origin contract did not exist.
• cargo test -p hft-collector (195 passed, 2 ignored)
• cargo clippy -p hft-collector --lib -- -D warnings
• single-file rustfmt check
• git diff --check
• two independent read-only final reviews: no blockers.

A PRD is unnecessary because issue #222 already specifies the behavior and this is one independently reviewable source/collection contract.

Rollout / rollback impact

No executable or deployment behavior changes. This module is dormant until the later CLI/deployment layers use it. Rollback is a single code revert.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 5 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: 1014e844-e527-42ff-b078-31e3c311118d

📥 Commits

Reviewing files that changed from the base of the PR and between 05d1966 and 9a47d4f.

📒 Files selected for processing (2)

• rust_hft/tools/collector/src/binance_usdm_reference_collector.rs
• rust_hft/tools/collector/src/lib.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cex-usdm-reference-runtime-222

---

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