test: validate Polymarket v2 end-to-end environments

[md0x]

Summary

• Add versioned Staging VNet and Amoy manifests with deployment history, runtime hashes, UUPS topology, source/ABI provenance, ownership, roles, allowlists, and cross-contract bindings.
• Add read-only fork checks plus a full Forge-local VNet lifecycle from Polymarket request registration through Managed OO settlement, the reporter callback, aggregator finalization, and binary payout.
• Document reproducible setup, provenance checks, event evidence, funding/reset behavior, and the supported Amoy subset and blockers.

This targets unaudited-pm-v2-oo-reporter because the fixtures validate the post-audit integration currently proposed in #65.

Validation

• forge test --no-match-contract '.*Fork.*' -vv — 83 passed
• PolymarketV2ManifestTest — 1 passed
• PolymarketV2VNetWiringForkTest — 3 passed
• PolymarketV2EndToEndForkTest — 2 passed
• PolymarketV2AmoyWiringForkTest at the pinned snapshot — 3 passed
• Amoy latest-state mode — 2 passed, 1 expected historical-check skip
• Clean environment without RPC variables — manifest passes, 8 fork tests skip explicitly
• Source, ABI, deployment-record, and Git-blob provenance check — passed

Safety and environment scope

All lifecycle mutations run inside Forge's disposable local EVM. The suite contains no broadcast path, signer, private key, service credential, or remote impersonation/write method.

Amoy passes the exact wiring and authorization subset. Its automatic lifecycle remains blocked because the deployed reporter is the base OOReporter and OOReporterModule has no selected operator.

Linear: FRO-111

[linear]

FRO-111

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 46889d0042

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

[chatgpt-codex-connector]

Propagate jq failures from provenance extraction

When jq is unavailable or cannot parse a manifest, it runs inside a process substitution whose failure is not propagated by the surrounding while loop, even with set -euo pipefail. All three loops can therefore process zero records and the script still exits successfully with “provenance verified,” leaving the advertised source and ABI checks bypassed. Capture and validate each jq result before iterating, or otherwise explicitly wait for and check the producer status.

Useful? React with 👍 / 👎.