From 61a25a5a4089429920b743572b6ad1d4a1e4fa03 Mon Sep 17 00:00:00 2001
From: autonomic-bot <autonomic-bot@git.autonomic.zone>
Date: Fri, 12 Jun 2026 23:45:38 +0000
Subject: [PATCH] review(cfold): record ghost follow-up audit

---
 machine-docs/REVIEW-cfold.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/machine-docs/REVIEW-cfold.md b/machine-docs/REVIEW-cfold.md
index 4bf1fbc..d4cb53c 100644
--- a/machine-docs/REVIEW-cfold.md
+++ b/machine-docs/REVIEW-cfold.md
@@ -148,3 +148,28 @@ the formal `claim(cfold): M2 ...` handoff and the required all-green full sweep
   cfold-neutral upgrade-path failure rather than custom-test discovery loss.
 
 Verdict: no new finding and no gate pending. Waiting for a formal `M2` claim or a Builder inbox message.
+
+---
+
+## 2026-06-12T23:45:11Z — Cold Ghost follow-up audit; still no formal M2 claim
+
+- Cold rebase in `/srv/cc-ci/cc-ci-adv`: `git pull --rebase` -> `Already up to date.`
+- `machine-docs/STATUS-cfold.md` still shows `## M2 — IN PROGRESS`; there is still no
+  `Gate: M2 — CLAIMED, awaiting Adversary` WHAT/HOW/EXPECTED/WHERE payload to verify.
+- Independent cold artifact check on cc-ci continues to support the Builder's current framing of the
+  lone remaining `ghost` deviation as cfold-neutral rather than a custom-tier discovery drop:
+  - `ssh cc-ci "jq '{level, recipe, stages: (.stages | map({name, status}))}' /var/lib/cc-ci-runs/557/results.json"`
+    -> `level: 1`, `recipe: ghost`, passing stages only 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 "printf '557 custom='; ls /var/lib/cc-ci-runs/557/junit/custom__cc-ci__*.xml | wc -l; printf ' 557 upgrade='; ls /var/lib/cc-ci-runs/557/junit/upgrade*.xml 2>/dev/null | wc -l; printf ' 559 custom='; ls /var/lib/cc-ci-runs/559/junit/custom__cc-ci__*.xml | wc -l; printf ' 559 upgrade='; ls /var/lib/cc-ci-runs/559/junit/upgrade*.xml 2>/dev/null | wc -l; printf ' 185 custom='; ls /var/lib/cc-ci-runs/185/junit/custom__cc-ci__*.xml | wc -l; printf ' 185 upgrade='; ls /var/lib/cc-ci-runs/185/junit/upgrade*.xml 2>/dev/null | wc -l"`
+    -> `557 custom=4 557 upgrade=0 559 custom=4 559 upgrade=0 185 custom=4 185 upgrade=2`.
+  - `ssh cc-ci "printf '557 ref='; grep -R -n 'd88f5801' /var/lib/cc-ci-runs/557/abra/recipes/ghost/.git | wc -l; printf ' 559 ref='; grep -R -n 'd42d0f7c' /var/lib/cc-ci-runs/559/abra/recipes/ghost/.git | wc -l"`
+    -> both runs confirm the expected checked-out Ghost refs are present in the run artifacts.
+- Interpretation: fresh runs `557` and `559` still execute the canonical four-file `tests/ghost/custom/`
+  set, but fail before producing any upgrade-tier junit files. Historical run `185` has both the same
+  four custom junit files and two upgrade junit files, reinforcing that the regression remains in the
+  Ghost upgrade path rather than in cfold's custom-folder migration.
+
+Verdict: no new finding and no gate pending. `M2` still cannot PASS until the sweep is formally claimed
+and all recipes are green.