Publish and deploy a source-bound Polymarket quote runner

[proerror77]

Parent

#326

What to build

Publish and deploy an immutable bare-metal Polymarket quote-runner release from one exact source revision so the production market-tape service emits the quote status fields required by the candidate Rust uploader. The rollout must verify the installed binary and service identity, preserve the prior binary as the rollback target, and prove a newly closed production segment passes the real-segment uploader preflight before any long shadow Gate begins.

Acceptance criteria

• The release workflow publishes the bare-metal quote runner with source revision, binary SHA-256, and a release manifest suitable for independent readback.
• Deployment verifies the artifact and version, installs it atomically, records rollback evidence, and does not alter the reference collector or uploader identities.
• The running quote service is bound to the reviewed binary SHA and remains restart-free through a normal segment boundary.
• Newly written quote records contain explicit successful request and collection-result fields; collection failures are represented explicitly rather than inferred.
• The first newly closed production segment passes issue Preflight Rust uploader with a real closed Polymarket segment #420's exact candidate upload and OSS readback preflight.
• Sequence continuity, reconnect/failure counters, and the prior binary rollback path are recorded after rollout.
• Research/snapshot logic and Capture full-update Polymarket CLOB evidence for token microstructure research #235 are unchanged.

Blocked by

#420 must merge before the production rollout. Implementation may proceed independently.

Out of scope

Relaxing candidate uploader validation, changing snapshot construction, evaluator/MCTS behavior, reference collection, uploader cutover, and #235.

[proerror77]

清账标记（2026-08-04）：#420 已关闭，但本 issue 的验收仍包括制品发布、生产安装、回滚身份和真实闭合段 preflight/readback，属于 runtime 交付而非无人认领的纯代码任务。需由具名 controller 在独立 runtime 操作中收尾；暂不关闭。