Release readiness and go-live gates

1. Current release snapshot

2. QA and user-flow gates

1. Wallet connect and network switch verified on desktop + mobile wallet browser.
2. Create alliance flow verified with valid and invalid participant/share payloads.
3. Funding path verified: approve, deposit, progress indicators, remaining calculations.
4. Acquisition governance path verified: `voteToAcquire` then `buyNFT` execution only after quorum.
5. Sale flow verified: vote sale, execute sale, proceeds split/claim path.
6. Refund path verified under failed funding, including pause interaction behavior.
7. Error states verified: wrong network, wallet reject, RPC 429, stale address mismatch.

3. Quality gates before publish

• `next build` succeeds without type/runtime errors.
• ESLint passes for app and integration surfaces.
• Environment variables audited and synchronized with deployments page.
• Docs updated in same release (deployments, assumptions, runbook, changelog).
• RPC fallback URLs configured to reduce single-provider downtime risk.
• Explorer links from homepage and docs verified manually.

4. Security and policy gates

• Trust assumptions are published clearly on homepage/docs.
• Known limitations are published (unsupported token mechanics, faucet cooldown, NFT approval preconditions).
• Rules of use, reporting path, and security contacts are published.
• No private keys, RPC secrets, or local-only values are committed in public repository.