Supervise formal Polymarket raw-ops Gate

[proerror77]

Change contract

Run each formal Polymarket raw-ops Gate as one bounded, queryable systemd-supervised job with an immutable candidate and invocation identity, so Cloud Assistant can request operations without owning the Gate process tree.

Out of scope

• Artifact-bundle inclusion, immutable staging, operator documentation, and CI/release integration are owned by Polymarket raw-ops: atomically stage an exact immutable release #449.
• Production installation, formal Gate execution, cutover, collector/uploader changes, research, snapshots, and Capture full-update Polymarket CLOB evidence for token microstructure research #235 are unchanged.
• This PR is not deploy-ready. Do not deploy or run the production Gate from this PR; Polymarket raw-ops: atomically stage an exact immutable release #449 must complete the deployment integration first.

Dependency or merge order

• Code dependency: None; the final reviewed branch is rebased onto exact main a98f26d93ce8c40c05466713de7c43b251fbd671.
• Merge order: merge this code contract first; Polymarket raw-ops: atomically stage an exact immutable release #449 may then integrate the paired controller/unit/Gate assets into the immutable release and deployment path.

Focused validation

• RED -> GREEN counterexamples cover controller disappearance, duplicate start, post-start InvocationID read failure containment, finalize-time shadow readback failure receipts, cancellation, abnormal exit, finalizer-only pass promotion, missing official evidence, paired-unit mismatch, symlink rejection, exact fake-systemctl argument shapes, and inherited-fd lock retention/release.
• Terminal commit counterexamples inject failures at .receipt.json.tmp -> .receipt.json.ready, .receipt.json.commit -> receipt.json, and staged-journal cleanup. Before durable receipt publication PASSED.sha256 is absent; status idempotently validates and completes each interrupted commit.
• Failed terminal cleanup removes the actual Gate temporary marker ..PASSED.sha256.ready.tmp.
• bash deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• bash -n deployment/aliyun/polymarket-raw-ops-gate-control.sh deployment/aliyun/polymarket-raw-ops-shadow-gate.sh deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• shellcheck deployment/aliyun/polymarket-raw-ops-gate-control.sh deployment/aliyun/polymarket-raw-ops-shadow-gate.sh deployment/aliyun/test-polymarket-raw-ops-control-plane.sh
• Replayed the exact CI Rust-only/Python-command scanner from .github/workflows/ci.yml.
• git diff --check origin/main...HEAD
• Rebase range-diff: all three commits unchanged from reviewed base.
• Spec review: Erdos the 2nd — APPROVE.
• Standards review: Avicenna the 2nd — APPROVE.
• Additional concurrency/fail-closed review — APPROVE.
• CI-fixture code review: Ampere the 2nd — APPROVE.
• CI-fixture test review: Mendel the 2nd — APPROVE.
• Terminal commit code review (gate448_terminal_review) — APPROVE.
• Terminal commit test review (gate448_terminal_tests) — APPROVE.

Atomic exception

The final delta is +1195/-15, above the 750-line review guardrail. Erdos the 2nd (Spec), Avicenna the 2nd (Standards), gate448_terminal_review, and gate448_terminal_tests explicitly APPROVED the atomic exception. The controller, templated systemd unit, Gate-side exact-supervisor/ready-marker handshake, recoverable receipt/marker commit, and counterexample harness are one rollback and safety boundary. Splitting them would leave an unrunnable unit, a controller without Gate-side ownership/pass-promotion enforcement, or safety behavior without the regression proof needed to review it.

Rollout and rollback impact

• Rollout: no runtime mutation in this PR. After Polymarket raw-ops: atomically stage an exact immutable release #449 integrates and verifies the immutable release assets, operators can install the exact paired unit and controller, then start/status/cancel by candidate SHA and systemd invocation ID.
• Failure behavior: every non-pass removes staged/official pass markers, attempts to stop Rust shadow, preserves Python, and writes a failed or cancelled terminal receipt; query uncertainty stays failed-closed.
• Crash recovery: terminal receipt phases are validated and committed in order under one lock; the official pass marker is promoted only after a durable terminal receipt exists.
• Rollback: revert these commits before Polymarket raw-ops: atomically stage an exact immutable release #449 integration, or remove the integrated supervisor assets through Polymarket raw-ops: atomically stage an exact immutable release #449's deployment rollback contract. Existing Python production behavior is untouched.

Closes #448

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 5 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: 0201bcc4-ea80-47c2-9693-d89a24b29902

📥 Commits

Reviewing files that changed from the base of the PR and between a98f26d and 39bd447.

📒 Files selected for processing (4)

• deployment/aliyun/polymarket-raw-ops-gate-control.sh
• deployment/aliyun/polymarket-raw-ops-gate@.service
• deployment/aliyun/polymarket-raw-ops-shadow-gate.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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 369ac74cd3

ℹ️ 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".