fix(alpha): isolate blocking mission execution

[proerror77]

Change contract

Run only mission execute on a Tokio blocking worker so its synchronous HTTP, filesystem, database, and archive pipeline cannot create or drop blocking runtimes on the async dispatcher thread, while preserving the inner error chain.

Out of scope

• Prediction execute or snapshot dispatch; those are independently reviewable and will use a separate PR.
• Explicit execution-cost modeling or its evidence report; feat(alpha): model explicit execution costs and capacity #84 already owns that contract.
• Other mission commands, live execution, collector behavior, or broader async refactors.

Dependency or merge order

None. This PR is based directly on current main. Merge before the independent prediction-runner PR only to avoid overlapping cli.rs rebases; there is no behavioral dependency.

Focused validation

• cargo +1.91 fmt --manifest-path rust_hft/Cargo.toml --package alpha-harness -- --check
• CARGO_BUILD_JOBS=2 cargo +1.91 test --manifest-path rust_hft/Cargo.toml --locked -p alpha-harness (72 passed)
• CARGO_BUILD_JOBS=2 cargo +1.91 clippy --manifest-path rust_hft/Cargo.toml --locked -p alpha-harness --all-targets -- -D warnings
• Targeted counterexample: cli::tests::mission_execute_runs_blocking_pipeline_outside_async_runtime exercises mission execute under a current-thread Tokio runtime and verifies the original inner source error survives worker dispatch.
• Scope: 1 file, 58 additions, 1 deletion.

Rollout / rollback impact

Research CLI scheduling only. Mission output, validation, and fail-closed behavior are unchanged. Roll back by reverting this PR; no schema, data, deployment, or live-execution migration is involved.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 34 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: 009b029c-8e7e-4e6a-b5d2-276648948eb8

📥 Commits

Reviewing files that changed from the base of the PR and between 6b99cae and 5df2457.

📒 Files selected for processing (1)

• rust_hft/alpha-harness/app/src/cli.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/alpha-mission-blocking-runner

---

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