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
@@ -1,3 +1,15 @@
+## v0.266.0 — a failed install removes what it started (2026-09-23, R-649)
+
+**MinAgent: 0.131.0** (unchanged). No new strings. No hub change.
+
+- **Operator ruling 2026-09-23 (R-649):** when the deploy's `compose up -d` fails for its own reasons (e.g. a
+  dependency whose healthcheck never passes after its container started), `runComposeDeploy` now runs
+  `compose down` before recording „not deployed" — so „not installed" never stands over running
+  containers (R-634's promise, completed). `down` WITHOUT `-v`: named volumes are kept. A failed `down` is
+  logged; the household's Remove clears what is left (v0.262.0 `halfStateEvidence`).
+- Tests: `TestR649_AFailedInstallRemovesWhatItStarted` (stub compose, PATH = the stub only),
+  `TestR649_ASuccessfulInstallIsNotTakenDown`. Red-proof: the `down` removed → `calls=["up -d"]`.
+
 ## v0.265.0 — the cause of "runs but not installed", a held app that says so, a louder OOM storm (2026-09-23, R-634, R-625, R-636, R-647)

 **MinAgent: 0.131.0** (unchanged). **Needs hub v0.121.0** (deployed first). New strings: yes (hu + en).