fix(collector): pin PM tape validator contract for quote_collection_failure

[proerror77]

Change contract

Pin the PM tape upload validator's quote_collection_failure contract with regression tests. No production-code change: investigation (prompted by 14 retained segments on the Tokyo host failing unsupported update kind 'quote_collection_failure' since 2026-07-30T22:00) found the validator at main already supports the kind — the deployed host binary predates #239. This PR adds the missing regression coverage so the contract can't silently regress.

Out of scope

• Redeploying the current uploader binary to the host (runtime action, tracked in fix(collector): PM tape upload rejects quote_collection_failure kind, segments stuck since 2026-07-30 #533; once redeployed the 14 retained segments upload with no further code change)
• Recovery-path validation (validate_reference_tape_for_recovery) deliberately unchanged — quote kinds can never legitimately appear in reference tapes

Dependency / merge order

None. Independent. Merge first among the current batch.

Focused validation

• 6 new tests in polymarket_upload.rs: recorder-shaped tape with failure records passes (failures excluded from quote counts/coverage), 5 malformed variants fail closed
• cargo test -p hft-collector --locked: 58 polymarket_upload tests + full suite green

Rollout / rollback impact

None — tests only.

Issue relationship

Refs #533

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 59 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: 18fc2e2a-fc75-4ce8-9e68-2392d6fa1953

📥 Commits

Reviewing files that changed from the base of the PR and between 322372e and 2e79ac6.

📒 Files selected for processing (1)

• rust_hft/tools/collector/src/polymarket_upload.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.}