feat(alpha-harness): bind CEX MCTS research evidence

[proerror77]

Change contract

Bind the admitted Binance/CEX MCTS run to a versioned research identity, resume bounded checkpoint chunks fail-closed, and emit one typed receipt joining checkpoint, training evidence, selected candidate, and the single sealed evaluation.

Out of scope

• Polymarket evaluator or shared UCT behavior changes
• Store schema changes
• Collector or deployment changes
• Production/live trading or promotion rules

Dependency or merge order

Depends on Issue #401 / PR #409, already merged. The branch is rebased onto main after independent Issue #410 / PR #411. No stacked PR remains.

Focused validation

• cargo test -p alpha-domain: 38 passed
• cargo test -p alpha-engine: 77 passed, 1 real-LLM environment test ignored by design
• cargo test -p alpha-harness: 119 passed
• cargo clippy -p alpha-domain -p alpha-engine -p alpha-harness --all-targets -- -D warnings
• Exact rustfmt checks and git diff --check
• Two independent read-only reviews: PASS

Rollout or rollback impact

Research-only. Checkpoint schema v3 intentionally rejects stale v2 checkpoints. Rollback is a revert of this PR; there is no collector cutover, live execution authority, or deployment change.

Scope guardrail

5 files, 715 additions and 33 deletions, 748 non-generated changed lines; below the 750-line split-assessment threshold.

Closes #402

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 12 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: 04bded63-d9a6-45bc-ac65-ba8e550602d6

📥 Commits

Reviewing files that changed from the base of the PR and between 34fc015 and 4691be5.

📒 Files selected for processing (5)

• rust_hft/alpha-harness/app/src/mission.rs
• rust_hft/alpha-harness/app/src/mission_runner.rs
• rust_hft/alpha-harness/domain/src/lib.rs
• rust_hft/alpha-harness/engine/src/engines/mcts.rs
• rust_hft/alpha-harness/engine/src/engines/mod.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cex-shared-mcts-adapter-402

---

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