fix(collector): verify complete market tape coverage

[proerror77]

Relates to #224.

Change contract: Extend the market-tape data contract and strict verifier so SHA-bound exact stream coverage can certify static symbols without fabricating trades or depth updates, while preserving real Binance USD-M sequence-bridge state across segments.

Out of scope: Collector production, deployment/gate scripts, ECS cutover, historical reconstruction, snapshot construction, evaluator/MCTS, and research logic.

Dependency or merge order: None. This is layer A and must merge before the layer B producer/deployment PR. No production cutover is permitted between layers.

Focused validation:

• cargo test -p hft-data --lib (50 passed)
• cargo test -p hft-collector --bin lob-pit-materializer (4 passed)
• cargo clippy -p hft-data --lib -- -D warnings
• Generic binance.market_tape.v1 verifier compatibility is covered for the complete 2026-07-18 cohort shape.
• Counterexample covers static USD-M checkpoint followed by a cross-segment U=95,u=105,pu=90 overlap diff.
• Read-only specification and standards reviews approved.

Rollout/rollback impact: No producer or runtime rollout in this PR. Existing generic verifier behavior remains unchanged. Roll back this layer only after dependent layer B is rolled back.

PRD note: This is a small, already-specified verifier/data-contract defect under issue #224, so a separate PRD is unnecessary; implementation was driven by focused failing tests.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 40 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: 1f0d6521-3c5b-4eb7-a200-8e6973856e54

📥 Commits

Reviewing files that changed from the base of the PR and between 4201492 and 47655cd.

📒 Files selected for processing (4)

• rust_hft/data-pipelines/core/src/binance_lob_replay.rs
• rust_hft/data-pipelines/core/src/binance_market_tape.rs
• rust_hft/data-pipelines/core/src/binance_market_tape_artifact.rs
• rust_hft/tools/collector/src/bin/lob-pit-materializer.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cex-market-tape-verifier-224

---

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