fix(collector): bound async Polymarket OSS uploads

[proerror77]

Change contract

Run closed Polymarket OSS tape uploads asynchronously across source files with a bounded worker limit, while retaining the existing fail-closed data/manifest/_SUCCESS readback and source-deletion gate.

Issue relationship

None

Out of scope

Collector/reference-collector behavior, OSS permissions or objects, deployment scripts, production service state, and research/evaluator work.

Dependencies and merge order

None.

Focused validation

• cargo test -p hft-collector --lib --locked — 278 passed, 2 ignored.
• cargo test -p hft-collector --bin polymarket-raw-ops --locked — 7 passed.
• cargo clippy -p hft-collector --lib --bin polymarket-raw-ops --locked -- -D warnings.
• Counterexamples cover out-of-range concurrency, concurrent staging-root creation, and the bound of two simultaneous closed-source uploads.

Rollout and rollback

Deploy only after the normal raw-ops gate succeeds. Canary one closed source and independently read back data, manifest, and _SUCCESS before enabling the uploader timer. Roll back by restoring the prior release binary and keeping the timer disabled; unverified local sources remain because deletion follows readback only.

Scope exception

None.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 13 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: 4c09366c-17a2-4203-b20b-d0bf12304d8c

📥 Commits

Reviewing files that changed from the base of the PR and between fea372d and d5e7d10.

📒 Files selected for processing (2)

• rust_hft/tools/collector/src/bin/polymarket-raw-ops.rs
• 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.}