Upgrade coordination standard: every chain upgrade announced, tracked and reviewed in public

Original Proposal Text

A text proposal. It moves no funds and changes no parameter. It records what regen-1 expects from every software upgrade from here on. WHY. Proposal 79 (Regen Ledger v7.3.0) passed 62.1M yes to 0 no. At its upgrade height, 28,971,032 on 24 September 2026, the chain made no blocks from 14:58 to 16:29 UTC, about an hour and a half. When blocks resumed, 3 of the 11 validators were missing, together about 26% of voting power and the largest among them, so for that stretch the chain ran about 7 points above the two-thirds line where it halts again. No thread on forum.regen.network announced the proposal, the upgrade window or the outcome. Projects building on the chain and holders had no public signal before, during or after. THE STANDARD. For every software-upgrade proposal: 1. Announcement. A forum.regen.network thread is opened the day the proposal is submitted and linked in its metadata, with the upgrade height, the estimated time, the release with binaries and checksums, and a validator checklist. 2. Acknowledgement. Each active validator confirms in that thread, before the upgrade height, that it is ready. 3. Live status. During the upgrade window the thread carries status: the halt, the restart, which validators are signing. 4. Post-mortem. Within 7 days of the upgrade the thread carries a short post-mortem: how long block production stopped, which validators were late and why, and what changes next time. 5. Owner. The thread names the person responsible for these posts, and a backup. WHAT A YES MEANS. The chain expects this of every upgrade, and a yes voter will look for the thread before voting yes on the next one. Nothing here is enforced by code. WHAT A NO MEANS. Upgrades continue without a public standard. Discussion: the forum thread linked in this proposal's metadata. More details: https://forum.regen.network/t/v7-3-0-upgrade-what-happened-and-what-every-upgrade-needs-from-now-on/637