status(2): disk resize 30->70GB in progress (orchestrator) — disk-blocker LIFTING; deploys paused; plan to re-run lasuite-drive FULL lifecycle + mattermost after cc-ci healthy

machine-docs/DEFERRED.md

@@ -157,6 +157,11 @@ before the build is called done) — but does **not** force closure.
 - **Linked IDEA:** —
 
 ### 2026-05-29 — heavy-recipe upgrade tier needs more host disk (28GB too small)
+- [~] **LIFTING @2026-05-29:** operator/orchestrator is resizing the cc-ci VM disk **30→70GB** (VM
+      restart in progress). This removes the constraint. To fully CLOSE: after cc-ci is back + healthy,
+      re-run lasuite-drive's FULL lifecycle (incl. the upgrade tier) green + Adversary cold-verify, then
+      re-confirm immich/lasuite-meet/lasuite-docs upgrade tiers. Until that green run lands, the Q3.2
+      upgrade tier stays a veto-eligible open item per the Adversary's conditional-signoff model.
 - [ ] **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