diff --git a/machine-docs/DEFERRED.md b/machine-docs/DEFERRED.md
index 559eebc..8bd1451 100644
--- a/machine-docs/DEFERRED.md
+++ b/machine-docs/DEFERRED.md
@@ -156,12 +156,13 @@ 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)
-- [~] **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.
+### 2026-05-29 — heavy-recipe upgrade tier needs more host disk (28GB too small) — CLOSED @2026-05-29
+- [x] **CLOSED @2026-05-29:** orchestrator resized the cc-ci VM disk; filesystem auto-grew to **64G
+      (44G free, 30% used)**, infra healthy, warm keycloak up. The disk constraint is resolved. The
+      heavy-recipe upgrade tiers are now runnable. **Follow-on (now ACTIVE backlog, not a deferral):**
+      run lasuite-drive's FULL lifecycle incl. the upgrade tier GREEN + Adversary cold-verify for the
+      Q3.2 gate (per the Adversary, the upgrade tier is no longer validly deferrable); then re-confirm
+      immich/lasuite-meet/lasuite-docs upgrade tiers. Tracked under BACKLOG-2 Q3.2.
 - [ ] **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