Roll out the current Rust Polymarket collector into continuous ready-event publication

[proerror77]

Parent

#314

What to build

Replace the drifted production Polymarket data path with the reviewed exact-main Rust collector and qualification contract. Use a bounded shadow gate, independently verify current-schema OSS publication and ready-event catalog admission, then perform one named-controller cutover. Runtime evidence must bind source, image, configuration, and object identities; repository ancestry or service health alone is insufficient.

Acceptance criteria

• Preflight records current ECS and ACK ownership, deployed binary and configuration evidence, active automation, release lock, and immutable rollback identity.
• The candidate uses an exact-main immutable image from Publish ACR images from the smoke-tested exact-main release artifact #317 and records source SHA, image digest, configuration SHA, schema, producer, and verifier identity.
• A bounded shadow gate runs for at least one complete hour without clobber, watchdog conflict, sequence gaps, unexplained reconnect loss, or permanent retry loops.
• Current-schema market, reference, completion, and qualification objects are independently downloaded and rehashed.
• At least three consecutive BTC x 5m events enter the ready-event catalog with separate Up and Down books and correct Chainlink/settlement evidence.
• Cutover occurs under one named controller; the prior collector remains the explicit rollback target until post-cutover verification passes.
• Post-cutover evidence proves the canonical producer remains current-schema and continuously classifies ready, partial, and rejected events.
• Cleanup removes temporary shadow resources and reports retained capacity, watchdogs, queues, and rollback expiry.

Blocked by

#317, #318, and #319

Out of scope

Snapshot construction, Mission or evaluator changes, MCTS, Binance collector changes, Paper, Shadow trading, Live, and promotion.

[proerror77]

Runtime preflight (2026-07-26): #317/#318 are closed and #319 is now closed by merged PR #348, so code dependencies are satisfied.

No cutover has been started. Read-only infrastructure evidence shows the only dedicated production ECS is i-6we6afeqsvv8uo1ixmyo / monday-trade-data-26, explicitly tagged/described as the Binance market-data collector, while ACK has no active Polymarket Pod, Deployment, CronJob, or Job. The #326 systemd shadow/cutover contract requires a dedicated Polymarket target host and immutable candidate release; repurposing the Binance host or inventing an ACK deployment would change the runtime topology and violate this issue’s fail-closed rollout contract.

Next required action: provision or identify the dedicated Polymarket collector target, then run the existing one-hour shadow gate under the named controller before cutover.