diff --git a/cc-ci-plan/JOURNAL.md b/cc-ci-plan/JOURNAL.md
index 477d159..6c6aa5a 100644
--- a/cc-ci-plan/JOURNAL.md
+++ b/cc-ci-plan/JOURNAL.md
@@ -336,3 +336,17 @@ gzip/dump-path fix WORKS, marker restore test PASSED; remaining: app 502s after
 relayed via tmux.** Concurrency machinery observed working live: parallel immich+plausible runs held
 per-recipe locks, registered pidfiles, plausible's teardown unregistered cleanly. Immich run 4 =
 build 245 (custom, running) with both fixes live — monitor armed.
+
+### Event 2026-06-10 ~00:05 — IMMICH PR #2 GREEN (build 245, level=4); cc-ci PR #9 merged; plausible go-ahead
+**Immich PR #2 (head a92b28d) verdict: GREEN** — build 245, ALL tiers pass (install/upgrade/backup/
+restore/custom), level=4, deploy-count 1/1, PR-side VERDICT=GREEN via testme poller, zero leakage
+(no stacks/volumes, active-run registry empty). The 1.7.0+v2.7.5 upgrade + no-DROP pg backup/restore
+is fully CI-verified; merge decision is the operator's. Run history: 6 RED pre-handover → 238 RED
+(backup 409, convergence gap) → 241 hung (paused-update flag) → 245 GREEN. **cc-ci PR #9 merged**
+(157d06d, push build 246 green): assistant3's one-flag test fix (psql -q in plausible
+_register_site — command tags polluted the compared output; assertion unchanged, reviewed: no gate
+weakening). Caught an UNSUBMITTED "PR #9 is merged, go ahead" sitting in assistant3's tmux prompt
+BEFORE it was true — verified state=open first, merged it, synced builder-clone, then submitted the
+go-ahead. Plausible !testme on PR #3 (head 270c840, incl. their 502-after-restore + --if-exists
+fixes) is now assistant3's trigger; cc-ci main has every prerequisite landed. Open: plausible verdict
+(#11), final session wrap.