fix(alpha): gate CEX MCTS on immutable baseline evidence

[proerror77]

Change contract

Before any CEX MCTS transition, replay and verify the exact Factor Bank, Ridge, CART, and frozen baseline gate from the registry. Reject invalid or failed evidence. Remove obsolete CEX Formula-MCTS executable identity/constructor; fail closed pending the #601 adapter.

Issue relationship

Closes #600

Out of scope

• Replace CEX formula-growing MCTS with Factor-Bank subset selection #601 subset search
• Emit a four-stage deterministic strategy and combination walk-forward evidence #602 strategy
• event replay
• sealed holdout
• Paper/Shadow/LiveSmall
• collector/ClickHouse/runtime/deployment

Dependencies and merge order

• Dependencies already merged: feat(alpha): add typed CEX baseline evidence contract #662, feat(alpha): evaluate deterministic Ridge and CART baselines #663, fix(alpha): verify CEX baseline evidence lineage #668, feat(alpha): persist immutable CEX baseline evidence #664.
• Base: origin/main@e13b1f79647336c83d699a51cf3c7011701d9eb8.
• Merge order: this PR after the listed dependencies.

Focused validation

• alpha-engine: 83/83 tests passed.
• alpha-harness: 135/135 tests passed.
• alpha-engine and alpha-harness scoped Clippy all-targets with -D warnings passed.
• cargo fmt -p alpha-engine -p alpha-harness -- --check passed.
• git diff --check passed.
• .github/scripts/agent-worktree-preflight.sh passed (verdict=ok).
• Counterexamples: tampered gate and domain-valid failed gate remain Pending with zero iterations; valid gate reaches the Replace CEX formula-growing MCTS with Factor-Bank subset selection #601-required refusal.

Rollout and rollback

Research-only; no runtime mutation. Roll back this PR before #601.

Scope exception

None (4 files, 499+/222-, below threshold).

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 11 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: 0dd5dcd3-9cd1-4533-a388-bf51d16cc371

📥 Commits

Reviewing files that changed from the base of the PR and between e13b1f7 and 71f749d.

📒 Files selected for processing (4)

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

---

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