test(rfc64): align live gate timeout window

[branarakic]

User impact

A valid testnet synchronization that takes longer than two minutes no longer fails the M1 proof harness before the exact VM/SWM observation is returned. The gate remains bounded and fail-closed: the shipped live launcher owns the 25-minute policy, passes it explicitly to the generic process bridge, and still supports an explicit override.

Before

sequenceDiagram
  participant G as M1 gate
  participant A as Testnet adapter
  participant E as Edge node
  G->>A: synchronize-edge
  A->>E: Durable and SWM catch-up
  E-->>A: Catch-up complete
  G--xA: 120-second outer timeout
  A-->>G: Late exact snapshot
  G-->>G: Reject unknown sequence

Loading

After

sequenceDiagram
  participant L as Live launcher
  participant G as Generic process bridge
  participant A as Testnet adapter
  participant E as Edge node
  L->>G: Explicit 25-minute live bound
  G->>A: synchronize-edge
  A->>E: Durable and SWM catch-up
  E-->>A: Catch-up complete
  A->>E: Read exact VM and SWM state
  E-->>A: Exact snapshot
  A-->>G: Sequence-bound result within live bound
  G-->>L: Continue live-cold-restart proof

Loading

Validation

• pnpm test:m1:rfc64-selective-coverage:unit
• node --experimental-strip-types --test devnet/rfc64-m1-selective-coverage/live-launcher-config.test.ts
• pnpm typecheck:m1:rfc64-selective-coverage
• git diff --check

Stack

Base: #2047 (codex/rfc64-m1-public-priority)

[otReviewAgent]

Review Agent completed this review and found no issues.

[otReviewAgent]

Review Agent completed this review and found no issues.