Publish the Polymarket baseline E2E completion proof

[proerror77]

Parent

#314

Change contract

Publish one immutable completion manifest for the successful baseline cloud run from #233, binding the exact mission, snapshot, evaluator, MCTS, settlement, Up execution, and Down execution artifacts, then verify every object by a fresh digest readback.

Acceptance evidence

• The completion manifest has a versioned schema and binds exact main git SHA plus image digest.
• It records mission SHA, snapshot archive SHA, snapshot contract hash, evaluator report SHAs, MCTS checkpoint and outcome SHAs, and separate settlement, Up, and Down artifact SHAs.
• Every referenced object is downloaded through the canonical cloud path and rehashed successfully.
• The manifest names missing Binance surfaces, one-second L2 sampling, event count, held-out boundaries, and all unavailable claims.
• No local path, mutable latest pointer, service health check, or job success status substitutes for artifact readback.
• The final status distinguishes runnable research evidence from Paper, Shadow, Live, and profitability readiness.
• A missing, mismatched, or mutable artifact makes completion fail closed.

Out of scope

Research logic; snapshot construction; evaluator reruns; collector deployment; Paper or Live; promotion; deletion of earlier artifacts.

Dependency and merge order

Depends on successful #233. This is the separate result-publication issue required by the repository workflow.

Focused validation

Validate the manifest schema, every SHA-256, object identity, and no-clobber behavior. Attach the exact readback evidence to this issue.

Rollout and rollback impact

Append-only research publication. Rollback never rewrites or deletes prior evidence; an invalid publication is superseded by a new immutable manifest.