ops: qualify companion, Storage V2 snapshots, and soak evidence

[TheJudii]

The repository contains hardened reference services, readiness checks, alert rules, atomic snapshot/restore tooling, and signed release automation. Production promotion still requires network-specific evidence and immutable external inputs.

• Pin a reviewed telos-consensus-client release tag, source commit, binary digest, and passing two-parameter Engine contract test.
• Link ghcr.io/telosnetwork/telos-reth to this repository; make this repository's Actions workflows the sole writer of versioned tags; remove PAT, manual, and other-repository publishers; and record package recovery ownership.
• Produce mainnet and testnet Storage V2 bootstrap snapshots with block/hash, schema, source/companion digests, checksums, and remote immutable object IDs.
• Complete measured restore drills for both networks and record achieved RPO/RTO plus canonical head/hash parity.
• Exercise alert delivery, nodeos/companion outages, disk-full behavior, rollback, and snapshot failure semantics on production-like hosts.
• Complete at least 72 hours of testnet soak, then shadow-mainnet replay/parity including a forced reorg and restart.
• Record the prior known-good image/snapshot pair and named rollback/on-call owners in the release evidence.

No telos-v* release should be promoted until this checklist and the revm 41 execution blocker are closed.