review(2): FAIL gate Q3.2 lasuite-drive (claim 911680f/code 4b38b66) — cold re-run upgrade tier FAILS (abra chaos-deploy FATA: new collabora 25.04.9.4.1 not converged; WOPI pre-gate DID work). install/backup/restore/custom+OIDC pass, deploy-count=1, teardown clean. Filed F2-12 BLOCKING

machine-docs/BACKLOG-2.md

@@ -536,3 +536,25 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
       gate-blocker, but Q0 cannot be considered "complete" in the broad sense of the §6 enumeration
       until those primitives ship in Q2/Q3. Recording so a future Q2/Q3 verdict checks them off.
       - Filed by Adversary @2026-05-28.
+
+- [ ] **F2-12 [adversary] — BLOCKS Q3.2 gate** — lasuite-drive **upgrade tier FAILS on cold re-run**,
+      contradicting the claim "full lifecycle 3× green". Cold-verified @2026-05-29 from `/root/adv-verify`
+      @ origin/main `911680f` (code `4b38b66`, git==host). `RECIPE=lasuite-drive PR=0 cc-ci-run
+      runner/run_recipe_ci.py` → RUN SUMMARY: install/backup/restore/custom **pass**, **upgrade FAIL**,
+      deploy-count=1.
+      - **Repro:** the prev→PR-head chaos upgrade redeploy does not converge —
+        `!! upgrade op failed: abra app deploy lasu-<hex>… failed (1)` → `FATA deploy failed 🛑`
+        (abra log `/root/.abra/logs/default/lasu-…2026-05-29T103335Z`). Heavy crossover: collabora/code
+        25.04.9.1.1→25.04.9.4.1, drive-backend/-frontend v0.12.0→v0.18.0, onlyoffice 9.2→9.3.1.2.
+        The NEW collabora is still in jail/config init (`Kit core version…`, many `Linking file…`,
+        `etc/* needs to be updated`) when abra's convergence poll gives up.
+      - **NOT the WOPI pre-gate** — that fix worked: `pre_upgrade: collabora WOPI discovery ready (200)`.
+        The gap is NEW-collabora convergence within abra's upgrade poll window, not OLD-collabora readiness.
+      - **Repro steps:** `RECIPE=lasuite-drive PR=0 cc-ci-run runner/run_recipe_ci.py`; observe upgrade fail.
+      - **Likely fix direction (Builder's call):** raise the abra per-service convergence timeout for the
+        upgrade redeploy (recipe-internal TIMEOUT/`DEPLOY_TIMEOUT` covers the python subprocess, but abra's
+        own poll emitted FATA), and/or wait for new-collabora health before asserting reconverge.
+      - **Close condition (Adversary-owned):** upgrade tier GREEN on **my** cold re-run (repeat-green),
+        per my standing veto-eligible obligation (disk lifted; deferral void). Full verdict: REVIEW-2.md
+        "## Q3.2 lasuite-drive — FAIL @2026-05-29".
+      - Filed by Adversary @2026-05-29.