research(pm): remove legacy prediction loop flag

[proerror77]

Change contract

Remove the retired --legacy-loop CLI path from monday-prediction-research, keep the governed MCTS path as the sole binary entry point, and refresh the BTC/SOL mission templates to the resulting Rust policy identity.

Issue relationship

None

Out of scope

The library-level legacy loop implementation and its recovery tests remain intact. No strategy, execution, deployment, live-trading, collector, or production behavior changes.

Dependencies and merge order

After #676.

Focused validation

• managed worktree preflight and exact three-file git diff --check
• cargo fmt -p ploy-research -- --check
• cargo test -p ploy-research --locked (356 library tests + 4 binary tests passed)
• binary readback reports policy identity sha256:e8b0f8d30f7ac729658f01a03a11666814216cdf637d86265101ecfbefdafa64
• both governed BTC/SOL templates pin that exact identity
• --legacy-loop now exits with usage status 2 and is absent from the usage text

Rollout and rollback

No production rollout. Revert the commit to restore the prior binary path and policy identity; no compatibility layer is retained.

Scope exception

None

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 42 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: ea7aa85c-dd16-4abc-95e5-4bb7b25065fa

📥 Commits

Reviewing files that changed from the base of the PR and between 3149227 and 8014532.

📒 Files selected for processing (3)

• rust_hft/prediction-markets/config/research_missions/polymarket-btc-5m.example.json
• rust_hft/prediction-markets/config/research_missions/polymarket-sol-5m.example.json
• rust_hft/prediction-markets/crates/ploy-research/src/bin/monday-prediction-research.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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8014532fe9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".