review(2): resume checkpoint — no gate pending; drone block genuine (/etc/timezone still absent on host); leftover drone smoke stack flagged (housekeeping); immich P4-restore still OPEN, unsigned

machine-docs/REVIEW-2.md

@@ -1461,3 +1461,27 @@ justified. No VETO. Advances P1 coverage (mailu enrolled).
 **Isolation note:** verdict formed from the plan + code (lifecycle/abra/run_recipe_ci + the mailu test
 files) + STATUS claim verification info + my own two cold re-runs + direct recipe/host inspection.
 JOURNAL-2 not consulted before this verdict.
+
+---
+## Resume checkpoint @2026-05-29T22:35Z (spend-limit lift; cold re-orient)
+Pulled to `1857733`. **No gate is CLAIMED awaiting Adversary.** State of play:
+- **Q4.2 mumble — PASS** (REVIEW-2 `1daa1ea`, ACK `e36656f`). DONE.
+- **Q4.9 mailu — PASS** (REVIEW-2 `2958eb6`, ACK `25ae293`). DONE.
+- **Q4.6 discourse — deferral VERIFIED SOUND** (`594f2d3`); upstream bitnami images gone (§8 env-blocker).
+- **Q4.10 drone — BLOCKED, deferral genuine.** Re-entry trigger is `ssh cc-ci 'cat /etc/timezone' = UTC`.
+  Cold-checked the host: **`/etc/timezone` is still absent** (`ls: cannot access '/etc/timezone'`), so the
+  gitea SCM dep still can't boot and the block is real — operator host-deploy of `3bde76f` has NOT landed.
+  Integration is scoped (JOURNAL-2 `f86a58a`); I'll weigh the §4.3 build-creation §7.1 sign-off only once
+  the maximal subset is actually run green (not pre-clearing un-built content).
+- **Q3.5 immich — P4 restore RED still OPEN** (BACKLOG-2 Q3.5): upstream recipe uses live-volume backup
+  (no pg_dump hook) → postgres `ci_marker` doesn't survive restore. Builder to choose recipe-PR vs §7.1
+  sign-off on the maximal subset; I have NOT signed off — this is a real P4 gap on a claimed-enrolled recipe.
+- **Q5.1 docs (`1857733`) landed** but is not claimed as a gate; P8 verification deferred until claimed.
+
+**Break-it probe — leftover stack on cc-ci (housekeeping, NOT a gate-FAIL).** `docker stack ls` shows a
+`drone_ci_commoninternet_net` stack (app `drone/drone:2.26.0` 1/1, deployed ~2d ago, task failures at
+15h/32h/2d) + volume `drone_ci_commoninternet_net_data`, left over from the drone+gitea smoke. drone is
+not claimed DONE so this is not a teardown-gate failure, but the node is NOT "clean" — flagged to Builder
+inbox (same housekeeping class as the prior `mumb-smoke`/`mail-smoke` leftovers; remove at leisure or
+confirm it's intentional pre-staging for the post-host-fix integration). `warm-keycloak` (warm SSO dep),
+`backups`, `ccci-bridge`, `ccci-dashboard`, `traefik` are expected infra.