docs: release skills re-verify every networks.md figure against sources of truth

[AztecBot]

Generalizes the verification lessons from the v5.0.1 docs release (#24763) — specifically from cross-checking the machine-derived networks.md values against the hand-written ones in #24756 — into the /release-docs and /release-network-docs skills, so every future release re-checks all of it against sources of truth instead of trusting carried-forward or hand-transcribed values.

The two discrepancies that cross-check caught, which motivate the rules:

• The mainnet rollup version was hand-converted from 0xfd39c8f7 and shipped wrong (4248094967 instead of 4248422647).
• The Alpha Execution Delay was carried forward as 30 days when the live Governance.getConfiguration() says 2 days — the governance table had no re-verification step at all.

What the skills now require, every release

A new "Re-verify every figure against its source of truth" subsection in /release-docs Step 9 (referenced from /release-network-docs Step 4), plus a Key Point:

• EIP-55 checksums: every L1 address goes through cast to-check-sum-address before landing in the tables.
• Decimal conversions: on-chain hex is converted with cast to-dec, never by eye.
• Rollup version: read from each network's rollup via getVersion() and cross-checked against the RPC's rollupVersion; in the pre-release flow the target rollup's on-chain value wins.
• L1 chain id: cast chain-id must agree with the docs row and the node RPC's l1ChainId.
• Governance parameters table (previously never mentioned by the skills): queried on-chain for both columns — Proposer Quorum from the Governance Proposer (QUORUM_SIZE/ROUND_SIZE), Voting/Execution delays from Governance.getConfiguration() decoded against the tag's IGovernance struct (with a warning about the 256-second compressed time fields), Slashing Quorum/Round Size from the Tally Slashing Proposer (QUORUM, ROUND_SIZE, ROUND_SIZE_IN_EPOCHS).
• Cross-check human-owned data: when the network team has a parallel deployment update in flight, diff every value against it and resolve discrepancies by querying the chain, then reconcile with the owner before shipping.

Stacked on #24763 (which already added the cast to-dec note and the migration-notes TBD rule); once that merges this PR retargets to next and carries only these two skill files.

---

Created by claudebox · group: slackbot · Slack thread