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