journal: bridge one-comment-per-!testme deployed; note cc-ci deploy-path gap

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

cc-ci-plan/JOURNAL.md

@@ -240,3 +240,16 @@ The overnight runner finished and pinged the orchestrator; morning report at `/s
 - **Skipped (4):** bluesky-pds / mumble / lasuite-drive up-to-date; immich — abra can't parse tag+digest image refs (explanatory comment left on PR#1).
 - **abra-auth issue:** confirmed = go-git needs creds embedded in `origin` URL (ignores insteadOf/.netrc); recovered all 8 at runtime; skills now fixed (this session). TTY `script` wrapper was a separate, also-correct fix.
 - **Operator follow-ups:** (a) a few recipes now have 2 open PRs — an upgrade PR alongside a prior backup-fix PR (discourse #2+#1, ghost #3+#1, mattermost-lts #2+#1, plausible #2+#1) — reconcile/close the superseded ones; (b) re-run matrix-synapse + discourse with `--with-tests` to refresh the stale tests; (c) mattermost-lts + plausible failures are pre-existing recipe bugs to investigate.
+
+### Event 2026-06-02 ~17:30 — bridge: one comment per !testme (deployed)
+Operator wanted each `!testme` to get its OWN comment (edited in place to that run's result), instead of
+the old "reuse/edit one marker comment in place" (which made re-runs on an unchanged head invisible).
+Changed `bridge/bridge.py` `process_testme`: always `post_comment` a fresh ⏳ placeholder per run;
+`watch_and_reflect` still edits THAT run's `cid` to ✅/❌. cc-ci repo commit `a78ec2d` (pushed).
+- **Deployed to the live cc-ci server.** ⚠️ Deploy-path gap: the documented `/root/cc-ci` is GONE.
+  Deployed via `/root/builder-clone` (the harness's host clone — has the real remote + the `secrets`
+  submodule): `git pull origin main` → `git submodule update --init secrets` →
+  `nixos-rebuild switch --flake '/root/builder-clone?submodules=1#cc-ci'`. Diff was bridge-only (no
+  other nix/ changes), so only the bridge image rolled (content-hash tag 3761c42→4482ce9). Verified:
+  new image Running, poller watching all 20 repos. **Follow-up:** establish a clean canonical deploy
+  checkout for the cc-ci server (not the harness's builder-clone).