plan: queue proxy and ghost follow-up phases

cc-ci-plan/JOURNAL.md

@@ -558,3 +558,23 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private
   though `opencode attach` has no `--model` flag: it now injects `OPENCODE_CONFIG_CONTENT`
   for the session. Verified live: `cc-ci-orchestrator-oc` tmux session running on
   `backend=opencode model=openai/gpt-5.4`, visible through the shared web server.
+
+## 2026-06-12 ~15:55 — OpenCode GPT-5.4 loops resumed; durable proxy phases queued
+- Operator switched orchestration from Claude to OpenCode/GPT-5.4 and requested the remaining work be
+  made explicit: durable Swarm proxy fix, post-proxy verification, and ghost re-evaluation.
+- Added phase plans:
+  `plan-phase-pvfix-swarm-proxy.md`, `plan-phase-pvcheck-post-proxy-verification.md`,
+  `plan-phase-ghost-reeval.md`.
+- Persisted phase queue is now:
+  `rcust;shot;lvl5;bsky;dstamp;mailu;kuma;mailu;drone;cfold;pvfix;pvcheck;ghost`, with idx still
+  `9` (`cfold`) so the loops finish the already-started custom-folder phase before the proxy and ghost
+  follow-ups.
+- Replaced stale Claude `cc-ci-orchestrator` tmux session (was parked on a weekly-limit banner) with an
+  OpenCode session using `openai/gpt-5.4`; builder/adversary restarted with
+  `LOOP_BACKEND=opencode LOOP_MODEL=openai/gpt-5.4 ADV_MODEL=openai/gpt-5.4 RESUME_PHASE=1`.
+- Watchdog bug fixed in `launch.py`: it now treats only the configured `ORCH_SESSION` tmux session as
+  orchestrator liveness and restarts it if the pane command does not match the expected backend. This
+  prevents stale Claude one-shot/report sessions from masking a missing OpenCode orchestrator.
+- Verified live tmux mapping: `cc-ci-builder`, `cc-ci-adv`, and `cc-ci-orchestrator` are all `opencode`;
+  `cc-ci-watchdog` is running. The watchdog will hourly-wake `cc-ci-orchestrator` via the existing
+  `ORCH_WAKE_INTERVAL=3600` path and will apply the existing limit-window nudge/restart handling.