fix(polymarket): require Gate terminal receipt for cutover

[proerror77]

Change contract

Make raw-ops cutover consume and validate the exact immutable Gate terminal receipt before any production mutation, so a standalone gate.json cannot bypass terminal-success or shadow-containment checks.

Out of scope

• Gate supervision or staging behavior
• Market recorder and uploader data contracts
• Legacy Python implementation
• Research, snapshot, evaluator/MCTS, and Capture full-update Polymarket CLOB evidence for token microstructure research #235
• Production cutover itself

Dependency or merge order

• Depends on fix(polymarket): stage exact raw-ops releases #483 already merged into main at 9a58ff1
• No stacked PR dependency after merge; this branch is based directly on main

Focused validation

• bash -n deployment/aliyun/polymarket-raw-ops-cutover.sh deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• shellcheck deployment/aliyun/polymarket-raw-ops-cutover.sh deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• ./deployment/aliyun/test-polymarket-raw-ops-control-plane.sh

Rollout/rollback impact

• Rollout: control-plane only; cutover now requires a root-owned immutable terminal receipt bound to the exact Gate evidence
• Rollback: revert this PR to restore prior cutover admission behavior

Closes #484

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 34 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: 18a5f6a5-4e58-4f91-afee-ff4f0814ebc5

📥 Commits

Reviewing files that changed from the base of the PR and between 9a58ff1 and 13fb5ae.

📒 Files selected for processing (3)

• deployment/aliyun/README.md
• deployment/aliyun/polymarket-raw-ops-cutover.sh
• deployment/aliyun/test-polymarket-raw-ops-control-plane.sh

---

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