feat(data): expose bridged Binance L2 replay snapshots

[proerror77]

Change contract

Expose a deterministic, price-sorted full Binance L2 replay snapshot only after ReplaySequenceValidator reaches a bridged state.

Acceptance evidence

• cargo test --locked -p hft-data (15 passed on merged feat(data): validate Binance market tape #104 base)
• cargo fmt -p hft-data -- --check
• cargo clippy --locked -p hft-data --all-targets -- -D warnings
• cargo check --locked -p hft-data --all-targets
• git diff --check
• Independent review: APPROVE, zero findings

Out of scope

Tape schema and clock validation (#104), artifact manifest/checksum/compiler wiring, collector changes, databases, L3/order IDs, queue/impact/capacity/fill modeling, and live execution.

Dependency or merge order

None. This change is independently usable and does not depend on #104.

Focused validation

The counterexample test proves an unbridged replay cannot expose a book snapshot. The positive test applies a bridging diff, verifies deletions and updates, and asserts full bid-descending / ask-ascending deterministic output.

Rollout / rollback impact

No runtime wiring or behavior changes until a downstream consumer calls the new method. Roll back by reverting this PR; existing replay validation behavior is unchanged.

[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: 25 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

Run ID: a7057c75-c787-48d5-903b-42cce7a3c945

📥 Commits

Reviewing files that changed from the base of the PR and between 18a29bd and 6d0d0bc.

📒 Files selected for processing (1)

• rust_hft/data-pipelines/core/src/binance_lob_replay.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/binance-replay-book-snapshot

---

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