feat(market-data): expose verified manifest identity

[proerror77]

Change contract

Carry the already authenticated manifest SHA-256 through SealedPolymarketEvidenceTriplet into the trust-bearing VerifiedPolymarketEvidence identity so downstream research lineage can depend only on the verified handle.

Out of scope

• Trust-anchor construction or validation changes
• URI, object key, version, or ETag identity
• Polymarket semantic validation changes
• Research projection or snapshot assembly
• Publisher digest output from feat(polymarket): return published evidence digests #110

Dependency or merge order

None for this PR. The follow-up research projection must merge after this PR so it can record both authenticated content and manifest digests without accepting a second raw trust input.

Focused validation

• Red first: focused tests failed because neither sealed nor verified identity exposed manifest_sha256.
• cargo test -p ploy-market-data polymarket_evidence -- --nocapture (15 passed)
• cargo test -p ploy-market-data (21 passed)
• cargo clippy -p ploy-market-data --all-targets --no-deps -- -D warnings
• rustfmt --edition 2021 --check .../artifact.rs .../verified.rs
• Independent review: no P0-P3 findings.

The targeted identity test compares the sealed manifest digest with the exact bound manifest bytes. Existing tamper tests continue to prove that changed manifest bytes fail closed before a handle is created.

Rollout/rollback impact

Rollout: downstream research code may read the new identity field only from VerifiedPolymarketEvidence; detached identity data remains non-authoritative.

Rollback: revert this PR and keep the research consumer blocked from publishing manifest lineage. Do not replace it with a raw string supplied directly to research code.

[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: a58cdf16-a024-4c75-9fb1-762b3276e100

📥 Commits

Reviewing files that changed from the base of the PR and between a6e24b0 and 3416599.

📒 Files selected for processing (2)

• rust_hft/prediction-markets/crates/ploy-market-data/src/polymarket_evidence/artifact.rs
• rust_hft/prediction-markets/crates/ploy-market-data/src/polymarket_evidence/verified.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/polymarket-verified-manifest-identity

---

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]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.