review(2): Q4.7 plausible teardown CLOSED (plau-0c70fd fully clean); cold run done, node FREE; §4.3 first-hand PASS still pending; inbox-notify Builder mumble unblocked

machine-docs/REVIEW-2.md

@@ -1291,3 +1291,21 @@ documented-deferral-under-scrutiny, not a refuted gate. To upgrade to a first-ha
 single clean cold run (after a GitHub-rate-limit cooldown) where ClickHouse converges and both
 `*_event_roundtrip` tests PASS in my own re-run. Pending items: confirm my hung cold run tears down
 its `plau-0c70fd` stack cleanly (runner auto-teardown; will verify).
+
+### Q4.7 plausible — teardown obligation CLOSED + cold-run terminal state @2026-05-29T~18:57Z
+Confirmed on cc-ci (cold): my cold run **completed** (no longer hung — RUN SUMMARY printed). It did
+NOT reach the custom tier:
+- `prepull: no images resolved (config --images rc=15) — skipping`
+- compose-validity warning: `service "app" depends on undefined service "events_db": invalid compose
+  project` (events_db filtered as obsolete in this version's compose selection)
+- `!! deploy/readiness failed: plau-0c70fd...: not healthy over HTTPS /api/health (last status 404)`
+- RUN SUMMARY: deploy-count=1, **install: fail**, upgrade/backup/restore/custom: **skip**.
+
+**Teardown obligation CLOSED — fully clean.** `docker stack ls` shows NO `plau` stack; `docker
+service ls --filter name=plau` empty; `docker volume ls | grep plau` (none); `docker network ls |
+grep plau` (none); no `run_recipe_ci` process alive. The runner auto-teardown reclaimed everything.
+
+**§4.3 first-hand PASS still NOT obtained** (my run failed at install/readiness before the custom
+tier). My consolidated verdict stands unchanged: §4.3 content non-vacuous + shown green once in the
+Builder `instcustom.log`; full lifecycle unproven; no VETO, no gate-FAIL. The single-node is now FREE
+(my plausible cold run done) — Builder unblocked to run the Q4.2 mumble full harness.