Peter Steinberger 48447a63c6 fix(update): restore Gateway and clear stale warnings after repair (#151003) ... Complete update repair recovery after successful acknowledgement or failed finalization. Keep Gateway maintenance custody in the update parent, fence expired mutation work, and restore and verify the owned service before preserving the original failure exit. Doctor children do not activate their parent's Gateway. Clear acknowledged recovery warnings and actions in CLI and Control UI reports while retaining historical failure records. Reuse the existing Doctor maintenance, activation deadline, and update ledger owners. Preserve recovery guidance for ordinary maintenance refusals and legacy failed-history handling without adding configuration, CLI options, database schema changes, or dependencies. Related: #150950 #151132. Also related: #150942. Reported by @shadesurgeon. Validation: exact-head CI run 35284407181 passed with zero pending checks; committed-branch review is scoped-clean. Existing proof includes 430 selected tests, 177 survivor tooling tests, changed-file and import-cycle checks, and the published 2026.9.4-driver Linux qualification. The injected 15000 ms plugin deadline refused a late config write, restored the Gateway, released custody, and retained exit code 1. That qualification uses a systemd fixture with real Gateway processes. Synthetic before/after screenshots show cleared recovery prompts with historical failures preserved.		2026-09-17 16:36:11 -07:00
..
how-updates-run.md	fix(update): stop returning exit 0 for detached, unfinished updates (#150799)	2026-09-17 10:15:36 -07:00
repair-and-recovery.md	fix(update): restore Gateway and clear stale warnings after repair (#151003)	2026-09-17 16:36:11 -07:00
status-and-history.md	fix(update): keep starting Gateways running after readiness timeouts (#149760)	2026-09-16 01:47:40 -07:00