Chain upgrades batched into one planned jump; monitoring to be hardened

Nothing shipped. Two decisions were written down about how Satsuma's chain is run. First, two pending patch releases of the chain's node software will be skipped in favour of one planned jump to the next release line. That jump waits for the new line's first or second monthly patch, around December, and must finish before the current line's support ends in March 2027. The reasoning: "Against that, every rollout costs three restarts, and each restart pauses finality until the node is back. Two rollouts carry more risk than one. Waiting is the better trade."

Second, a survey of monitoring options concluded: "Verdict: don't build a monitoring service from scratch. You already have one." The existing watchdog, a 111-line script that checks the chain every minute and pushes alerts, will be hardened instead. The plan adds the checks it is missing, keeps a history, and makes alerts reach the operator through Do Not Disturb and allows them to be acknowledged. The upgrade itself still needs to be planned as a project, and there is no disk-space alert yet.