status(cfold): record fresh ghost probe

2026-06-13 00:14:11 +00:00
parent 626773d5f7
commit fb8762acb9
2 changed files with 112 additions and 12 deletions
--- a/machine-docs/JOURNAL-cfold.md
+++ b/machine-docs/JOURNAL-cfold.md
@ -248,4 +248,98 @@ Conclusion:
  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.
+  change was justified by that audit alone.
+
+## 2026-06-13 — Ghost PR #3 fresh probe after reopen: same upgrade-only failure, plus duplicate trigger signal
+
+I looked for the smallest allowed M2 step that did not touch recipe code: reuse an existing Ghost PR head
+that had historically gone green and rerun it through the live `!testme` path.
+
+Actions taken:
+
+```bash
+$ set -a && . /srv/cc-ci/.testenv && set +a
+$ curl -fsS -u "$GITEA_USERNAME:$GITEA_PASSWORD" -X PATCH \
+    -H 'Content-Type: application/json' \
+    -d '{"state":"open"}' \
+    "https://$GITEA_URL/api/v1/repos/recipe-maintainers/ghost/pulls/3"
+# PR #3 reopened; head remains 720faa0bebc46a34857b2933df1924ccabbd4087
+
+$ curl -fsS -u "$GITEA_USERNAME:$GITEA_PASSWORD" -X POST \
+    -H 'Content-Type: application/json' \
+    -d '{"body":"!testme"}' \
+    "https://$GITEA_URL/api/v1/repos/recipe-maintainers/ghost/issues/3/comments"
+# comment 14497 created at 2026-06-13T00:07:50Z
+```
+
+Fresh live outcomes:
+
+```bash
+$ ssh cc-ci 'jq "{run_id, pr, recipe, ref, level, results, stages: (.stages | map({name,status,summary}))}" /var/lib/cc-ci-runs/568/results.json'
+{
+  "run_id": "568",
+  "pr": "3",
+  "recipe": "ghost",
+  "ref": "720faa0bebc4",
+  "level": 1,
+  "results": {
+    "backup": "pass",
+    "custom": "pass",
+    "install": "pass",
+    "restore": "pass",
+    "upgrade": "fail"
+  },
+  "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 'jq "{run_id, pr, recipe, ref, level, finished, results, stages: (.stages | map({name,status}))}" /var/lib/cc-ci-runs/569/results.json'
+{
+  "run_id": "569",
+  "pr": "3",
+  "recipe": "ghost",
+  "ref": "720faa0bebc4",
+  "level": 1,
+  "finished": 1781309502.5494862,
+  "results": {
+    "backup": "pass",
+    "custom": "pass",
+    "install": "pass",
+    "restore": "pass",
+    "upgrade": "fail"
+  },
+  "stages": [
+    {"name": "install", "status": "pass"},
+    {"name": "backup", "status": "pass"},
+    {"name": "restore", "status": "pass"},
+    {"name": "custom", "status": "pass"},
+    {"name": "lint", "status": "pass"}
+  ]
+}
+```
+
+Comment-stream evidence for duplicate triggers from one `!testme`:
+
+```bash
+$ curl -fsS -u "$GITEA_USERNAME:$GITEA_PASSWORD" \
+    "https://$GITEA_URL/api/v1/repos/recipe-maintainers/ghost/issues/3/comments?limit=20"
+# ...
+# 14497: !testme (2026-06-13T00:07:50Z)
+# 14498: cc-ci failure comment for run 568 (2026-06-13T00:08:05Z)
+# 14499: cc-ci in-progress comment for run 569 (2026-06-13T00:08:05Z)
+# 14500: cc-ci in-progress comment for run 570 (2026-06-13T00:08:05Z)
+```
+
+Takeaways:
+
+- Ghost is now freshly red post-cfold on three distinct PR heads (`720faa0b`, `d88f5801`, `d42d0f7c`), all
+  with the same upgrade-only failure shape while custom discovery stays green.
+- That further weakens any cfold-local explanation; the blocker remains in Ghost's live upgrade path.
+- There is also likely a separate trigger dedupe problem: one `!testme` comment spawned runs `568`, `569`,
+  and `570`. I did not broaden into a D1 investigation in this loop step because cfold M2 is already
+  hard-blocked by Ghost's repeated upgrade failures, but the evidence is now recorded.