PRD: isolate a Polymarket evidence compiler image

[proerror77]

This was generated by AI during triage.

Problem Statement

Polymarket research compilation currently has no Polymarket-named OCI publication path. The only image containing polymarket-raw-ops is published as a Binance LOB image, which mixes venue identity and makes a Polymarket-only research Job appear to depend on Binance infrastructure.

Solution

Publish one immutable, Polymarket-named compiler image. It contains only the existing Rust polymarket-raw-ops compiler and the existing OSS client needed by the research-only compile Job. The GitHub workflow reports a source-SHA-bound digest; #173 consumes that digest only.

User Stories

1. As a Polymarket researcher, I want the evidence compiler image to be named for Polymarket, so the runtime boundary matches the venue being researched.
2. As an operator, I want an immutable image digest tied to its source revision, so a cloud evidence Job is reproducible.
3. As a reviewer, I want the Binance LOB image and its host-release artifact unchanged, so this correction cannot alter Binance collection.
4. As a research Job controller, I want to use the existing Polymarket compiler command and OSS client without introducing a second compiler implementation.

Implementation Decisions

• Add one Polymarket-specific OCI target to the existing ACR publication workflow.
• Build the existing Rust Polymarket compiler command and the existing OSS client; do not copy the Binance LOB binary into this image.
• Emit and consume a digest reference, never a mutable tag.
• Keep the existing Binance LOB and research-runner publication targets unchanged.

Testing Decisions

• The ACR selector accepts the Polymarket target and rejects unsupported targets.
• The published image exposes the Polymarket compiler command and can authenticate an OSS read using the existing Kubernetes secret.
• A one-shot research-only Job records the exact source revision and image digest before compiling Compile matched BTC 5m LOB and reference evidence for snapshot input #173 evidence.

Out of Scope

• Polymarket collector deployment or cutover.
• Binance LOB image, service, host artifact, or data changes.
• Raw OSS evidence mutation.
• Evidence normalization, cohort construction, evaluator/MCTS, and live execution.

Further Notes

The single integration seam is the immutable digest reported by the ACR workflow. This is a prerequisite for, but not a change to, #173.

[proerror77]

Completed by merged PR #180 (Polymarket-only compiler image publication target).