fix(bridge): ignore pre-start trigger comments

machine-docs/STATUS-cfold.md

@@ -60,8 +60,9 @@ Current work item:
   a cfold-neutral upgrade regression on the recipe/environment side
 - fresh follow-up probes now show the Ghost upgrade failure is not confined to PR #4 / PR #5: a reopened
   PR #3 at ref `720faa0b` also re-failed twice post-cfold (`568`, `569`) with the same shape
-- one fresh `!testme` comment on Ghost PR #3 also spawned multiple runs (`568`, `569`, `570`), so there
-  is likely a duplicate-trigger side issue to investigate separately from cfold itself
+- 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
 
 ### M2 baseline matrix (built from live PR heads + fresh post-cfold evidence)
 
@@ -102,8 +103,12 @@ Current work item:
 - The fresh PR #3 rerun adds a second previously-green Ghost upgrade head that now fails the same way,
   so the blocker is broader than a single Ghost branch and still points away from cfold itself.
 - Side observation from the PR #3 retrigger: a single `!testme` comment at `2026-06-13T00:07:50Z` spawned
-  three new Ghost runs (`568`, `569`, `570`). `568` and `569` are already red with the same upgrade-only
-  failure; `570` was still in flight at the time of this status update.
+  three new Ghost runs (`568`, `569`, `570`). All three are now red with the same upgrade-only
+  failure.
+- Root cause of the triple-trigger: bridge logs show those three runs were tied to three distinct comment
+  ids on the reopened PR (`14029`, `14032`, `14497`), not one comment processed three times. The poller
+  replayed two historical `!testme` comments that predated the current bridge process because PR #3 was
+  closed during bridge startup and only became visible to the poller after reopen.
 - 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 across
   multiple Ghost PR heads as an upgrade convergence failure.
@@ -111,6 +116,8 @@ Current work item:
 ### Fresh Adversary state
 
 - `REVIEW-cfold.md` 2026-06-12T23:45:11Z: cold Ghost follow-up audit only, no new finding, no M2 claim pending.
+- `REVIEW-cfold.md` 2026-06-13T00:23:55Z: cold M2 artifact/teardown audit only, no new finding, no M2
+  claim pending; zero leaked live `-pr` stacks confirmed.
 
 ---