diff --git a/cc-ci-plan/JOURNAL.md b/cc-ci-plan/JOURNAL.md
index 11983a7..39f47b2 100644
--- a/cc-ci-plan/JOURNAL.md
+++ b/cc-ci-plan/JOURNAL.md
@@ -223,3 +223,11 @@ Phase 5 reached `## DONE` and the watchdog wrote SEQUENCE-COMPLETE at 23:23:43Z:
 - **Final mechanism = reboot-safe NixOS systemd timer.** Activated `cc-ci-upgrade-all.{service,timer}` (committed earlier as `ee58027`): **OnCalendar Sun 02:00 UTC, Persistent=true**, timer-triggered only (service not `wantedBy multi-user.target`). `nixos-rebuild switch` applied — only ADDED the two units, did NOT bounce anything (loops were already stopped). `systemctl list-timers` → next run **Sun 2026-06-07 02:00:00 UTC**. Retired the leftovers: busybox crond already gone, removed the inert `/home/loops/.cc-ci-crontabs/loops`.
 - **Operator-requested schedule change:** weekly upgrade moved from Mon 23:04 UTC (the phase-5 test schedule) to **Sun 02:00 UTC**.
 - **Stale note:** `cc-ci/machine-docs/DECISIONS.md` still records "§4 weekly cron: CronCreate" — now superseded by the NixOS timer. Left to the operator/next loop run to amend (cc-ci product repo, loops' single-writer domain).
+
+### Event 2026-06-02 03:42 — post-build work: mirror+regression phases DONE; overnight /upgrade-all running
+After the cc-ci build completed (2026-06-01), the operator drove a sequence of post-build phases via the loops:
+- **`mirror` phase DONE** (01:16Z): all recipes mirrored + enrolled (created mirrors for lasuite-drive/mailu/mumble; enrolled the 9 missing; loops did the live-host `nixos-rebuild #cc-ci` + `!testme` verification themselves after the deploy gate was removed — `#cc-ci` is safe since `be4f451`).
+- **`regression` phase DONE** (03:42:07Z) — **entire 2-phase sequence (mirror→regression) complete; loops + watchdog stopped/exited.** Shipped `tests/regression/` (cc-ci PR#5, NOT merged): **7 canaries, all Adversary cold-verified** — good-simple (custom-html-tiny) GREEN, good-significant (lasuite-docs) GREEN (5 tiers + clean teardown + no secret leak), bad-false-green RED, and 4 per-tier REDs (bad-install/upgrade/backup/restore, each RED at the intended tier with prior tiers passing; dedicated fixture recipes custom-html-bkp-bad / custom-html-rst-bad). 3 `@canary` + 4 `@canary_fast`; README documents the milestone-only cadence (not per-commit).
+- **PR consolidation (Assistant, one-shot):** every recipe mirror reduced to ≤1 open PR (custom-html #2→#1 @1.13.0; ghost #2→#1 = backup+upgrade). Verified one-open-PR-per-recipe across all mirrors.
+- **Overnight run in flight:** `cc-ci-overnight` (overnight-run.sh) gated on assistant-done + usage-reset + loops-idle, then launched the weekly **`/upgrade-all`** at 03:40Z (DEFAULT, never merges). It will write `/srv/cc-ci/.cc-ci-logs/overnight-report-<date>.md` and ping this session to deliver the operator's **morning** PushNotification (held until then — no overnight ping). The build-complete + regression-shipped headline will be folded into that morning notification.
+- **State:** watchdog/loops stopped by design (sequence complete → hourly wake stops too); the overnight runner + the weekly Sun-02:00 timer are the only live automation. Recipe-upgrade PR behavior was also reworked this session: never close unmerged PRs; extend an existing open upgrade PR by commit-on-top (no force-push) instead of a parallel PR; only close merged-upstream PRs.