research: align Polymarket projection with artifact audit

[proerror77]

Change contract

Project only canonical audit-usable Polymarket reference and order-book rows into research surfaces while preserving immutable raw evidence counts.

Out of scope

• ResearchSnapshot construction
• Factor-row freshness filtering
• Snapshot CLI and cloud E2E
• Collector, runtime, and deployment changes

Dependency or merge order

Base: main after #140. Merge before the refreshed verified-artifact snapshot adapter (#133), which passes the governed delay bound.

Focused validation

• Shared audit/projection usability predicates.
• A delayed newer-available book cannot replace a valid book.
• A delayed Chainlink reference is not projected.
• Valid plus extra delayed rows keep the audit Ok; rejected-only evidence remains Critical.
• Equal valid clocks remain ambiguous and fail closed.
• Non-positive projection cadence/delay is rejected.
• Linux heavy-feature policy test recomputed and pinned mission hash sha256:cfbcbd1df107d0e6d70a4bb6fcdf45bba97cba3bbbf30dd92b71423fd8be8b69 from final formatted source bytes.
• git diff --check is clean.
• No local Cargo/rustfmt was used; GitHub Linux CI is authoritative.

Rollout / rollback impact

Research-only projection behavior. Rollback is a straight revert before the dependent snapshot adapter.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 17 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: 25791ca4-2316-48b4-895f-519f389708ff

📥 Commits

Reviewing files that changed from the base of the PR and between d477cbb and 386e355.

📒 Files selected for processing (4)

• 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/polymarket_evidence_projection.rs
• rust_hft/prediction-markets/crates/ploy-research/src/verified_artifact_audit.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/polymarket-audit-usable-projection

---

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