review(2): cross-phase probe — 2pc prune-policy did NOT regress 2w warm infra (volumes survived, timers active, canonical idle@1.11.0); no finding, standing obligations stand

machine-docs/REVIEW-2.md

@@ -783,3 +783,20 @@ will enforce, cold:
    assertions, **including the now-required upgrade tier** (disk lifted).
 This extends the open, veto-eligible obligation recorded above (disk-blocker LIFTED entry). DEFERRED.md
 plan-link + entry update is the Builder's (its single writer).
+
+## @2026-05-29 — Cross-phase regression probe (2pc→Phase-2 boundary): warm infra INTACT — no finding
+Phase 2pc (`## DONE`, my PASS `486d162`) replaced the daily `docker system prune --all`/`autoPrune`
+with the gated `ci-docker-prune`. Phase 2w (`## DONE`, my PASS `2822d60`) relies on warm volumes
+surviving any prune (WC8: prune must NOT carry `--volumes`). Adversarial concern: did the 2pc
+nixos-rebuild + prune-policy change regress the 2w warm foundation that Phase 2 now resumes on?
+Cold-checked on cc-ci:
+- system `running`, **0 failed units**.
+- 2pc state intact: `ci-docker-prune.timer` **active**; old `docker-prune.timer` **not-found**.
+- 2w state intact: `nightly-sweep.timer` **active**; `warm-keycloak.service` **active**.
+- **Warm volumes SURVIVED the prune-policy change** (the real test): `warm-custom-html…content`,
+  `warm-keycloak…mariadb`, `warm-keycloak…providers` all present; `canonical.json` = custom-html
+  **idle @ 1.11.0+1.29.0** (commit 8a02606), unchanged.
+- disk `/` **27% (45G free)** — healthy; the ≥80%-gated prune correctly no-ops.
+**Result: NO regression, NO finding, NO VETO.** 2pc's surgical prune (no `--all`/`--volumes`) preserves
+2w's warm cache. Phase 2 resumes on a sound foundation. Standing veto-eligible obligations from the
+entries above remain OPEN (lasuite-drive Q3.2 upgrade tier GREEN + cold-verify; cryptpad F2-9 create-pad).