CEX: run USD-M reference collector with health evidence

[proerror77]

Change contract

Run the merged official Binance USD-M reference source and artifact contracts as a bounded interval/--once CLI with one-controller locking, persistent clocks, and atomic local health evidence.

Part of #222. This PR does not close the issue.

Out of scope

• source normalization and artifact schema changes
• systemd, ECS deployment/cutover, and shadow promotion gate
• issues CEX: 持仓结构、taker flow 与 liquidation collector #223 and CEX: WebSocket L2 delta 时序与连续性 collector #224
• snapshot, evaluator, and research logic

Dependency or merge order

Depends on merged PRs #253 and #254. Merge before the deployment bundle/shadow-gate layer.

Focused validation

• TDD red: valid bounded --once configuration initially failed with not implemented
• cargo test -p hft-collector --bin binance-usdm-reference-collector — 5 passed
• cargo test -p hft-collector — 200 library + 39 archiver + 13 other tests passed; 3 existing tests ignored
• cargo clippy -p hft-collector --bin binance-usdm-reference-collector -- -D warnings
• scoped rustfmt check and git diff --check
• independent Spec and Standards reviews: no blockers

Counterexamples cover zero limits, a second controller, lock symlink, API failure without fake artifacts, server-time receipt regression across attempts, and separate attempt/collection/readback completion clocks.

Rollout / rollback impact

Rollout: new binary only; no service or production host changes. Rollback: revert this PR without changing the merged source/artifact contracts or any research path.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 39 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: c0be343c-ed24-40da-9a0b-917116087e9e

📥 Commits

Reviewing files that changed from the base of the PR and between eab83cd and c66683e.

📒 Files selected for processing (2)

• rust_hft/tools/collector/Cargo.toml
• rust_hft/tools/collector/src/bin/binance-usdm-reference-collector.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cex-usdm-reference-cli-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.}