fix(polymarket): freeze legacy Gate health evidence

[proerror77]

Change contract

Freeze a fresh, fail-closed-clean legacy Python health snapshot at Shadow Gate start, require one newer fresh clean completed legacy cycle before pass, bind immutable startup/completion epochs exactly to both snapshots, and cap parity at the earlier of the legacy completion and continuously fresh Rust candidate.

Out of scope

Legacy collector behavior, snapshot/research logic, #235, Gate duration, parity verifier semantics, and immutable release replacement.

Dependency / merge order

Depends on #415, merged as e36d53c8e2f75390218581a74cb88c00318c9241. Merge this PR independently before building a new production artifact.

Focused validation

• RED: legacy evidence without a post-start clean cycle was accepted.
• RED: updated_at advanced while last_success_at stayed unchanged was accepted.
• RED: startup success epoch and inflated completion cutoff were not bound to their snapshots.
• GREEN: bash deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• git diff --check
• Two-axis final review: Standards 0 findings; Spec 0 findings.
• Counterexamples preserve Rust 240-second freshness while rejecting stopped or stale legacy evidence.

Rollout / rollback impact

After merge, build a new exact-main artifact and run a new 3600+601 second Shadow Gate. Production remains Python until immutable Gate evidence passes and cutover verification completes. Roll back by retaining the Python baseline and reverting this focused PR.

Closes #416

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 7 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: e5483f69-ec92-4c59-8807-727a2834da7f

📥 Commits

Reviewing files that changed from the base of the PR and between e36d53c and 6e4a4c2.

📒 Files selected for processing (3)

• deployment/aliyun/polymarket-raw-ops-shadow-gate.sh
• deployment/aliyun/polymarket-shadow-gate-policy.jq
• deployment/aliyun/test-polymarket-raw-ops-control-plane.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/polymarket-legacy-gate-freeze-416

---

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]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cac1a02a6b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".