docs: prepare Juno v30 mainnet upgrade

[juno-ai-dev]

Summary

• add the Juno v30 mainnet operator runbook targeting height 40420069
• follow the established Juno upgrade pattern: check out v30.0.0, verify the release commit, then make build && make install
• document the complete v29 → v30 migration and completed uni-7 evidence
• separate Cosmovisor/manual procedures and document signing-state-safe recovery

The unsigned governance payload will be constructed separately after merge so its operator-instructions URL can point to this repository's immutable merge commit.

Current live checks

• two providers report no current upgrade plan
• live gov authority is juno10d07y265gmmuvt4z0w9aw880jnsr700jvss730
• normal voting period is five days and minimum deposit is 5000 JUNO
• recent block-time samples place the target around August 3, roughly 14:17–16:26 UTC; height is authoritative
• full async-ICQ/channel refresh remains a quick pre-signing check

Verification

• the repository's v22 and v23 runbooks use the same git checkout <tag> / make build && make install pattern
• that exact pattern was executed from a clean detached v30.0.0 worktree using Go 1.25.2
• the source-built binary reported release commit c0b3a8d258d52d16e5bc39a75168a99aab9d098e, SDK v0.53.7, CometBFT v0.38.23, and wasmvm v3.0.4
• the source-built binary's libwasmvm dependency resolved successfully
• git diff --check passes
• no proposal template, prebuilt-binary downloader, image digest, or binary manifest is included

Remaining operational checks

• confirm >67% bonded voting power has built and staged the exact release commit and fee-floor config
• confirm snapshot/backup, incident ownership, and old v29 binary
• after merge, construct/generate/decode/hash the upstream-pinned unsigned proposal
• refresh live plan/governance/max-gas/async-ICQ state immediately before signing

No transaction was signed or broadcast.