diff --git a/machine-docs/REVIEW-cfold.md b/machine-docs/REVIEW-cfold.md
index 9ecec38..4d7c062 100644
--- a/machine-docs/REVIEW-cfold.md
+++ b/machine-docs/REVIEW-cfold.md
@@ -104,3 +104,33 @@ Verdict: no new finding and no gate pending. Waiting for a formal `M2` claim or
   references in docs/unit tests/discovery and the phase ledgers recording the migration history.
 
 Verdict: no new finding and no gate pending. Waiting for a formal `M2` claim or a Builder inbox message.
+
+---
+
+## 2026-06-12T22:41:00Z — Cold artifact audit after Builder M2 sweep snapshot; still no M2 claim
+
+- Cold rebase in `/srv/cc-ci/cc-ci-adv`: `git pull --rebase` -> fast-forward to `d24bb8f`
+  (`status(cfold): record M2 sweep snapshot`).
+- `machine-docs/STATUS-cfold.md` still shows `## M2 — IN PROGRESS`; there is still no
+  `Gate: M2 — CLAIMED, awaiting Adversary` WHAT/HOW/EXPECTED/WHERE handoff to verify, so no M2 PASS/FAIL
+  verdict is available yet.
+- Independent cold check of the blocking `ghost` deviation on the live cc-ci host is consistent with the
+  Builder's status note and points away from cfold itself:
+  - `ssh cc-ci "jq '{level, recipe, stages: (.stages | map({name, status}))}' /var/lib/cc-ci-runs/557/results.json"`
+    -> `level: 1`, `recipe: ghost`, stages present and passing for `install`, `backup`, `restore`, `custom`, `lint`.
+  - `ssh cc-ci "jq '{level, recipe, stages: (.stages | map({name, status}))}' /var/lib/cc-ci-runs/559/results.json"`
+    -> same shape: `level: 1`, `recipe: ghost`, same five passing stages.
+  - `ssh cc-ci "grep -R -n 'd88f5801' /var/lib/cc-ci-runs/557/abra/recipes/ghost/.git"`
+    shows build `557` checked out Ghost head `d88f580188c145b04484074079ddf6f37662d3a1`.
+  - `ssh cc-ci "grep -R -n 'd42d0f7c' /var/lib/cc-ci-runs/559/abra/recipes/ghost/.git"`
+    shows build `559` checked out the probe ref `d42d0f7c7cf9946077a583ffa3f7c96abfe94a77`.
+  - `ssh cc-ci "printf 'build557 custom junit count='; ls /var/lib/cc-ci-runs/557/junit/custom__cc-ci__*.xml | wc -l; printf 'build557 upgrade junit count='; ls /var/lib/cc-ci-runs/557/junit/upgrade*.xml 2>/dev/null | wc -l"`
+    -> `build557 custom junit count=4`, `build557 upgrade junit count=0`.
+  - `ssh cc-ci "printf 'build559 custom junit count='; ls /var/lib/cc-ci-runs/559/junit/custom__cc-ci__*.xml | wc -l; printf 'build559 upgrade junit count='; ls /var/lib/cc-ci-runs/559/junit/upgrade*.xml 2>/dev/null | wc -l"`
+    -> `build559 custom junit count=4`, `build559 upgrade junit count=0`.
+- Interpretation: both fresh Ghost runs executed the canonical `tests/ghost/custom/test_*.py` set (4 junit
+  files) and failed before any upgrade-tier junit artifact was produced. That supports the Builder's
+  current statement that Ghost is an upgrade-path regression, not a custom-folder coverage loss.
+
+Verdict: no new finding from this cold audit, but **M2 is not passable yet**. The phase still lacks both
+the formal `claim(cfold): M2 ...` handoff and the required all-green full sweep (`ghost` remains non-green).