fix(server): background server updates roll back unhealthy releases and announce restarts

- The launcher watches a committed update for a health period and rolls
  back a runtime that crashes after commit. The launcher protocol stays 3,
  so existing launchers keep running new runtimes.
- Clients hear about the restart before it happens, so they show the update
  as resuming instead of a lost connection.
- The release feed is checked again at the handoff, a newer release replaces
  a staged one, stable skips prereleases, mirrors must use HTTPS, and old
  runtimes are pruned.
24d41808d0maria-rcks committed on 10/11/2026, 7:30:30 AMparent4e53090
21 files changedLine totals unavailable