status(cfold): record ghost follow-up audit

machine-docs/JOURNAL-cfold.md

@@ -183,3 +183,69 @@ Adversary update pulled during this pass:
 - `review(cfold)` commit `93f56ae` added only an idle audit entry to `REVIEW-cfold.md`
 - no finding filed
 - no M2 PASS yet because no `claim(cfold): M2 ...` commit exists
+
+## 2026-06-12 — Follow-up Ghost artifact audit (same-ref historical pass vs fresh fail)
+
+Focused cold checks after the M2 sweep snapshot:
+
+```bash
+$ ssh cc-ci "jq '{level,recipe,ref,results,rungs,stages:(.stages|map({name,status}))}' /var/lib/cc-ci-runs/185/results.json"
+{
+  "level": 4,
+  "recipe": "ghost",
+  "ref": "d42d0f7c7cf9",
+  "results": {
+    "backup": "pass",
+    "custom": "pass",
+    "install": "pass",
+    "restore": "pass",
+    "upgrade": "pass"
+  },
+  "rungs": {
+    "backup_restore": "pass",
+    "functional": "pass",
+    "install": "pass",
+    "integration": "na",
+    "recipe_local": "na",
+    "upgrade": "pass"
+  },
+  "stages": [
+    {"name": "install", "status": "pass"},
+    {"name": "upgrade", "status": "pass"},
+    {"name": "backup", "status": "pass"},
+    {"name": "restore", "status": "pass"},
+    {"name": "custom", "status": "pass"}
+  ]
+}
+
+$ ssh cc-ci "jq '{level,recipe,stages:(.stages|map({name,status,summary}))}' /var/lib/cc-ci-runs/559/results.json"
+{
+  "level": 1,
+  "recipe": "ghost",
+  "stages": [
+    {"name": "install", "status": "pass", "summary": null},
+    {"name": "backup", "status": "pass", "summary": null},
+    {"name": "restore", "status": "pass", "summary": null},
+    {"name": "custom", "status": "pass", "summary": null},
+    {"name": "lint", "status": "pass", "summary": null}
+  ]
+}
+
+$ ssh cc-ci "grep -R -n \"start_period\" /var/lib/cc-ci-runs/559/abra/recipes/ghost"
+/var/lib/cc-ci-runs/559/abra/recipes/ghost/compose.yml:60:      start_period: 15m
+/var/lib/cc-ci-runs/559/abra/recipes/ghost/compose.yml:84:      start_period: 1m
+/var/lib/cc-ci-runs/559/abra/recipes/ghost/compose.ccci.yml:35:      start_period: 15m
+/var/lib/cc-ci-runs/559/abra/recipes/ghost/compose.ccci.yml:38:      start_period: 15m
+```
+
+Conclusion:
+
+- Historical build `185` passed the full Ghost lifecycle on the SAME ref now used in probe build `559`
+  (`d42d0f7c7cf9`), so the current M2 blocker is not tied to the `custom/` folder migration.
+- Fresh failing runs still execute the canonical 4-file `tests/ghost/custom/` suite and pass every
+  non-upgrade stage; the missing upgrade junit output remains the key symptom.
+- The current repo does not show an obvious cfold-local fix to apply: the Ghost-specific overlay is
+  unchanged, the recipe artifact still carries the expected `compose.ccci.yml` file, and the failure
+  remains in the live upgrade path rather than discovery/custom-test coverage.
+- Net: cfold remains blocked on a cfold-neutral Ghost upgrade regression / flake. No repo-local code
+  change was justified by this audit alone.

machine-docs/STATUS-cfold.md

@@ -58,6 +58,8 @@ Adversary verdict:
 Current work item:
 - full real-CI `!testme` sweep evidence is mostly assembled; one recipe (`ghost`) remains non-green for
   a cfold-neutral upgrade regression on the recipe/environment side
+- fresh artifact audit confirms historical build `185` passed on the same Ghost ref now failing in
+  probe build `559`, so no cfold-local code fix has been identified in this repo yet
 
 ### M2 baseline matrix (built from live PR heads + fresh post-cfold evidence)
 
@@ -93,6 +95,9 @@ Current work item:
 - To isolate cfold from recipe-head drift, a separate probe PR #5 was opened at Ghost's last known-green
   PR head `d42d0f7c` (historical build `185` = L4/L5-equivalent on 2026-06-05). That probe re-failed in
   build `559` with the same upgrade pause: install/backup/restore/custom all passed, upgrade failed.
+- Focused artifact audit after build `559` confirmed the same-ref comparison explicitly:
+  historical build `185` (`d42d0f7c7cf9`) had `upgrade=pass`, while fresh build `559` on that same ref
+  has `upgrade=fail` with the canonical `custom` stage still green.
 - Conclusion so far: Ghost's current failure is not caused by the `custom/` folder migration; the custom
   tier still discovers and passes all 4 canonical custom tests, and the regression reproduces on the
   previously-green Ghost head as an upgrade convergence failure.