-
v1.25.0 — crash resilience: systemd unit + systemd-aware restart
StableAll checks were successfulChecks / Functional checks (push) Successful in 15sreleased this
2026-09-26 00:17:38 +00:00 | 95 commits to main since this releaseThe observatory is a link in the orchestration chain (bells → broker → observatory → owner); its crash during the 2026-09-25/26 triple crisis needed a manual restart. v1.25.0 adds the safety net without changing the opt-in character.
zcode-observatory.service—Restart=on-failuresystemd user unit, deliberately NOT auto-enabled (owner preference);install.shtemplates the ExecStart path, installs the unit into~/.config/systemd/user/, reloads systemd and prints the enable command without running it (--no-unitopts out)observatory-restart.sh— preferssystemctl --user restartwhen the unit exists; the legacy fallback uses a bracketed pgrep pattern (the ps-grep predecessor killed its own shell on the station) and logs under XDG state (never/tmp, which the station wipes on reboot)- managed-parent steer spawns — the send-button and fastlane paths mark their dispatch children so the dispatcher’s v1.0.1 notification scope self-check keeps them in place: the fastlane branches on exit codes and the status view polls liveness, and a re-exec would fake deliveries
- tests pin the unit’s restart/opt-in contract, the restart script’s systemd branch, its self-kill-safe pattern and log location, and install.sh’s never-enables wiring
Pairs with zcode-dispatch v1.0.1 (broker restart policy + watchdog, scoped notification bells, canary infra group — its failures surface in the contract banner here).
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads