controller v0.266.0: a failed install removes what it started (R-649, operator ruling)

compose down (volumes kept) before the record reads not deployed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-23 18:06:29 +02:00
parent 411a43f8ef
commit 964ae7538f
4 changed files with 97 additions and 0 deletions
@@ -656,6 +656,11 @@ sentence, in the reader's language) and no Update button is rendered; the API st
 held update's error is stored as the key `update.error.held` and rendered per reader, so a reader in the
 other language than the box reads the hold in theirs (R-647).

+**A failed install removes what it started (v0.266.0, R-649, operator ruling 2026-09-23).** When the
+deploy's `compose up -d` fails, the controller runs `compose down` (WITHOUT `-v`: named volumes stay, so a
+reinstall after „keep my data" finds its data) before the record reads „not deployed". „Failed" therefore
+means nothing runs; the household presses Install again. A failed `down` is logged; Remove clears the rest.
+
 **Deploys are not interrupted (v0.265.0, R-634).** A deploy still running is not in any backup leg's app
 list, the volume leg asks again right before it stops an app, and `StopStack` / `StartStack` refuse a
 deploying stack (`ErrStackDeploying`) for every caller. Measured cause: the whole-box backup's `compose down`