[8.8] Soak run on the first scheduling public network

[rootwarp]

Plan reference: plan/glamsterdam-2026-09-05/issues/08-phase-8-network-soak-and-observability.md · Issue 8.8

Description

Run rs-vc across the Gloas activation epoch on the first public network that schedules it, collecting the daily snapshot from 8.7 and triaging every failed gate.

Implementation Notes

• Entry is a network config carrying a real GLOAS_FORK_EPOCH — read fork epochs, versions and every *_DUE_BPS* from that network's config file at run time; assume no value and no date. Scheduling is the gate; a calendar target never is.
• Run at least one day pre-activation, the boundary itself, and ≥ 14 consecutive days after; the window resets on a configuration change or a redeploy.
• Record each day's snapshot plus every fail-closed rejection (signer type/version, BN capability drop, PTC 204 bursts) with its triage verdict.
• Points cover setup, daily checks and the write-up; the 14 days are elapsed time. If a gate fails, the fix is a new issue in the owning phase, not scope creep here — and a fix that changes the deployed build restarts the 14-day window on the new build (D26); the soak describes one build only, the one 8.9b passed.

Acceptance Criteria

• ≥ 14 consecutive daily snapshots, all gates pass, on the exact rs-vc commit 8.9b's verdict names (recorded in every snapshot); a rebuild restarts the count.
• 0 slashable events: rvc_validators_slashed_total unchanged and no result="blocked" increment attributable to rs-vc.
• PTC submission rate ≥ 99% and attestation effectiveness ≥ 99% over the full window.
• Every fail-closed rejection observed is listed with a verdict (expected / defect + issue link).
• The activation-epoch transition is covered by a snapshot on both sides of the boundary.

Testing Notes

local keys first, then the remote-signer / DVT cluster; the network's own config files are the source of truth for epochs and deadlines.

Points: 3 · Type: chore · Priority: P0 · Scope: 1.5 days of effort across ≥ 14 elapsed days · Blocked by: #338, #341 (L1–L5 all green at the network's tag, D26) · Blocks: #342