[codex] Add combined Binance and Polymarket oracle E2E

[ByteYue]

Summary

This PR adds the Gravity Oracle transport and E2E surface for:

• Binance USD-M closed indexPriceKlines buckets through sourceType=3;
• finalized Polygon Polymarket CTF settlements through sourceType=6;
• fail-closed OracleState handling that preserves pending payloads across transient state failures.

The relayer-backed observations reuse the existing unsupported-JWK consensus path and execute agreed bytes through NativeOracle callbacks.

E2E coverage

The review surface is intentionally limited to three non-overlapping suites:

Suite	Network	Unique coverage
oracle_demo	Local mocks	Deterministic Binance plus binary Polymarket coexistence and combined frontend config
polymarket_mock	Local mock	Three-outcome match, random winner mapping, settlement, winner claim, and loser zero-claim
binance_price_feed_multivalidator	Binance public API	Four independent fetchers, 3-of-4 voting-power QC, onchain execution, and four-RPC replication

Follow-up commit 29a6bab01e addresses Galxe/gravity-audit#1033:

• removes the redundant standalone binance_price_feed suite;
• moves live frontend config output to the stronger four-validator suite;
• makes the shared Binance fixture directly executable as a Python module;
• rejects readiness accidentally satisfied by an unrelated process on the mock port;
• pins deterministic genesis files to contracts commit f5bd9a8079;
• consolidates repeated suite, MANUAL, workflow, and skill text into one canonical runbook.

This reduces the GitHub PR diff from 4613+/395- to 3586+/395- while retaining the distinct deterministic, three-outcome settlement, live-source, and quorum assertions.

Canonical runbook: gravity_e2e/docs/ORACLE_E2E.md.

Binance task semantics

binance_index_kline_v1 is continuous by definition. The task URI rejects the legacy continuous parameter. For each feedId, bucketStartMs and interval are immutable; use a new feedId when either changes. This keeps delivery nonce, bucket time, and confirmed-cursor reconciliation monotonic.

Run

Build once:

RUSTFLAGS="--cfg tokio_unstable" \
  cargo build --profile quick-release -p gravity_node -p gravity_cli --locked

Deterministic combined gate:

PATH="$HOME/.foundry/bin:$PWD/target/quick-release:$PATH" \
  ./gravity_e2e/run_test.sh oracle_demo --force-init

Focused three-outcome Polymarket gate:

PATH="$HOME/.foundry/bin:$PWD/target/quick-release:$PATH" \
  ./gravity_e2e/run_test.sh polymarket_mock --force-init

The live four-validator command, outbound approval boundary, replay parameter, frontend mode, stop commands, and expected evidence are maintained only in the canonical runbook.

Pinned revisions

• contracts: f5bd9a80794c318ea1ccdbd0fb7f15e1e83dbdad
• gravity-reth: 20af4ae4a2125f6232d6b2c5e7cc3f40140f2501
• gravity-aptos: 10c4553b16aead745e1701db7885a39313607b26
• gravity-sdk base: 10c491bc7fe69838398971281270ce438c72e17a

Cargo.lock contains one Aptos api-types revision.

Validation

Current cleanup commit:

• changed Python modules pass py_compile;
• all three retained pytest cases collect successfully;
• mock Binance module CLI and subprocess start/stop lifecycle pass locally;
• occupied-port ownership guard rejects readiness from an unrelated process;
• live frontend config schema generation passes;
• all retained TOML files parse;
• local Markdown links resolve;
• removed-suite and user-specific path scans pass;
• git diff --check passes.

The live four-validator suite previously passed at the pinned heads with four active validators, a 3-of-4 threshold, identical resolver rounds across four RPCs, and 1 passed in 47.97s.

Scope boundary

These suites prove configured task execution and contract consumption. They do not implement generic intra-epoch request discovery or automatic mirroring of arbitrary Polymarket UI markets. Production mirrors still require reviewed manifests, finality gates, watermarks, deadlines, and typed pending or expired states.