You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manual service restart (loopback only). A new --restart <service> verb in the privileged helper and a POST /api/v1/restart {project} route on the loopback API let a local caller (morfMonitor) request the restart of a stuck service. Deliberately narrow: the helper reuses the declared-target whitelist (declaredService), validates the unit and becomes root only after validation, then runs reset-failed + restart + is-active - never an arbitrary command, never a client-supplied path. The action reuses the operation journal (audit + single-active lock) and drives the existing Restarting → HealthCheck → Succeeded/Failed states (Queued → Restarting added to the state machine). The real systemd unit is resolved server-side from the declared target, never received from the client. Status is followed through the shared GET /api/v1/updates/<id> route. Linux first; the Windows branch fails cleanly and is left for the cross-host work.
