ci: package cached research binaries

[proerror77]

Change contract

When full Prediction Markets research-image smoke is selected, compile the six Linux release binaries in one cacheable Debian Bookworm job and make Docker package those exact artifacts without recompiling Rust.

Closes #236
Parent: #240

Out of scope

• ACR publish or cross-workflow artifact reuse
• Snapshot caching or mission dispatch
• ACK worker-pool or cloud rollout changes
• Collector, ResearchSnapshot, evaluator, MCTS, strategy, or live-runtime behavior

Dependency / merge order

Depends on merged PR #217. This is the first independent child of #240; #241 and #242 do not depend on its branch, while cloud rollout #243 waits for all three.

Focused validation

• go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.7 -color .github/workflows/ploy-ci.yml
• .github/scripts/test-select-prediction-image-smoke.sh
• git diff --check origin/main...HEAD
• Two independent read-only reviews: Standards APPROVE; Spec APPROVE
• This PR intentionally triggers the Linux Research image binaries and Research image smoke jobs, which are the authoritative proof that all six prebuilt entrypoints package and the policy/alpha-harness probes pass. The local host had no Docker daemon, so those Linux image probes were not claimed locally.

Rollout / rollback impact

Rollout affects only the selected CI image-smoke path. The default Docker target still source-builds for local compatibility. Rollback restores the smoke job to the default source-building Docker target; no deployed service, cloud worker, or runtime state changes.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 52 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: 88cbd4fa-3536-416c-94f0-1981d3fc0830

📥 Commits

Reviewing files that changed from the base of the PR and between 737e291 and b1dde9c.

📒 Files selected for processing (2)

• .github/workflows/ploy-ci.yml
• rust_hft/deployment/docker/Dockerfile.research

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/research-image-build-cache

---

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