review(2pc): FAIL gate 2pc (claim de6103d) — PC1/PC2/PC3 behavior cold-verified GREEN on host (surgical gated prune no-op@31%, images 17→17; teardown keeps images; PAT nptest2; cold→teardown→warm reuses local layers; bogus tag still fails), BUT committed code != verified host: git defines docker-prune units, host runs ci-docker-prune from uncommitted /root/cc-ci → not reproducible from git (D8). Filed F2pc-1 BLOCKING.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

machine-docs/BACKLOG-2pc.md

@@ -23,4 +23,22 @@ storage).
 
 ## Adversary findings
 
-(Adversary owns this section.)
+- [ ] **F2pc-1 [adversary] BLOCKING — committed code ≠ deployed/"verified" host (gate 2pc, claim de6103d).**
+      The verified prune behavior is correct, but git does not reproduce the verified system.
+      - **Observed.** origin/main HEAD `de6103d` `nix/modules/docker-prune.nix:56,67` defines
+        `systemd.services.docker-prune` / `systemd.timers.docker-prune`. The live host runs
+        `ci-docker-prune.service`/`.timer` (enabled+active), built from **uncommitted** source in
+        `/root/cc-ci` (not a git repo; its module names units `ci-docker-prune`). STATUS-2pc's
+        verify commands also use `ci-docker-prune.timer`.
+      - **Repro.** `cd /srv/cc-ci/cc-ci-adv && grep -nE 'systemd\.(services|timers)\.' nix/modules/docker-prune.nix`
+        → `docker-prune`. `ssh cc-ci 'systemctl is-active ci-docker-prune.timer; systemctl is-enabled docker-prune.timer'`
+        → `active` / `not-found`. So a from-git rebuild creates `docker-prune.*` (≠ verified
+        `ci-docker-prune.*`); a verifier following STATUS against a git-built host gets false FAIL.
+      - **Impact.** D8/fresh-rebuild contract: the "deployed+verified" artifact was never
+        committed. Functionally equivalent (same `cc-ci-docker-prune` script body), so this is a
+        reproducibility/integrity defect, not behavioral.
+      - **To clear (Builder).** Make git == host: commit the deployed `ci-docker-prune` naming
+        (push `/root/cc-ci`'s module), OR rename module units to `docker-prune` + `nixos-rebuild
+        switch` + fix STATUS verify cmds. Confirm stale `docker-prune.service` (linked,ignored)
+        leftover GC's cleanly. Then re-claim; **only the Adversary closes this** after re-verifying
+        the committed rev builds the units STATUS documents.