status(cfold): record live bridge rollout

machine-docs/JOURNAL-cfold.md

@@ -388,6 +388,19 @@ Verification:
 $ nix shell nixpkgs#python311Packages.pytest -c pytest tests/unit/test_bridge_trigger.py -q
 ..........                                                               [100%]
 10 passed in 0.04s
+
+$ ssh cc-ci 'nixos-rebuild switch --flake "git+file:///root/cfold-deploy?submodules=1#cc-ci"'
+# rebuild succeeded; deploy-bridge.service restarted and rolled the bridge task
+
+$ ssh cc-ci 'docker service inspect ccci-bridge_app --format "{{.Spec.TaskTemplate.ContainerSpec.Image}}"'
+cc-ci-bridge:eb32876581d9
+
+$ ssh cc-ci 'curl -fsS https://ci.commoninternet.net/hook/healthz'
+ok
+
+$ ssh cc-ci 'docker logs --since 5m 2088e44a0534 2>&1 | sed -n "1,80p"'
+poller (primary) watching ['recipe-maintainers/cc-ci', ..., 'recipe-maintainers/drone'] every 30s
+comment-bridge listening on 0.0.0.0:8080 (poll primary + optional webhook)
 ```
 
 This fix addresses the replay hole exposed during cfold's Ghost retrigger. It does not change the cfold

machine-docs/STATUS-cfold.md

@@ -62,7 +62,7 @@ Current work item:
   PR #3 at ref `720faa0b` also re-failed twice post-cfold (`568`, `569`) with the same shape
 - the Ghost duplicate-trigger side issue is now root-caused in the bridge source: reopened PRs can replay
   old pre-bridge-start `!testme` comments that were never seen during startup because the PR was closed
-  at that time; repo fix landed locally and is being carried through deployment verification
+  at that time; the bridge fix is now pushed and live on `cc-ci` (image tag `eb32876581d9`)
 
 ### M2 baseline matrix (built from live PR heads + fresh post-cfold evidence)