decisions/deferred(2): lasuite-drive upgrade tier = disk env-blocker (28GB host, dual multi-GB office image crossover); maximal subset in flight; operator disk-resize escalation; adversary heads-up

machine-docs/DEFERRED.md

@@ -156,6 +156,28 @@ before the build is called done) — but does **not** force closure.
   pluggable, not just claimed).
 - **Linked IDEA:** —
 
+### 2026-05-29 — heavy-recipe upgrade tier needs more host disk (28GB too small)
+- [ ] **What:** The upgrade tier for the heaviest recipes cannot complete on the 28GB host. Proven
+      on **lasuite-drive**: the prev→PR-head chaos upgrade crosses two multi-GB office image versions
+      at once — onlyoffice/documentserver-de `9.2 → 9.3.1.2` (3.94GB each) + collabora/code
+      `25.04.9.1.1 → 25.04.9.4.1` (~1GB) — so ~10GB of office images must coexist on disk during the
+      in-place rolling update. The host has only ~14GB docker headroom over its ~13GB baseline (nix
+      store ~9.6GB + infra images), so the PR-head pull hit 99% and the deploy failed. There is **no
+      harness mitigation** (the prev images are *running* when the new must be pulled — cannot `rmi` a
+      running image; nothing dangling to prune pre-upgrade). install/backup/restore/custom (single
+      version, ~6GB) all fit and pass — only the upgrade tier overflows. Almost certainly also blocks
+      the upgrade tier of other heavy recipes (lasuite-docs ships collabora; immich ships multi-GB ML
+      images; lasuite-meet).
+- **Filed by:** Builder, phase 2 (Q3.2 lasuite-drive full-lifecycle attempt)
+- **Reason for deferral:** Class A1 EXTERNAL infra input — host disk size. Not improvisable; not a
+      test-quality issue; the recipe legitimately bumps office image tags across releases.
+- **Operator action to lift:** grow the cc-ci host disk (resize the droplet volume + online-grow the
+      filesystem) to give heavy-recipe upgrade tiers transient headroom — ~+20GB would comfortably
+      cover the dual-office-version crossover and the rest of the heavy set. Then re-run the full
+      lasuite-drive lifecycle (and re-confirm immich/lasuite-meet/lasuite-docs upgrade tiers).
+- **Re-entry trigger:** operator disk resize, OR Phase-2b pull-through cache + image-GC policy work.
+- **Linked IDEA:** `cc-ci-plan/IDEAS.md` (pull-through cache / Phase 2b).
+
 ---
 
 ## Closed deferrals