plan: phase 'shot' — recipe screenshot audit & repair (queued after rcust)

Audit every enrolled recipe's CI badge/card screenshot, diagnose defects
(plausible null-every-run; ~4.8KB blank-frame SPAs: immich/lasuite-meet/
cryptpad/flaky n8n), fix via harness default-wait improvement first, per-recipe
SCREENSHOT hooks second; M1 audit matrix + M2 visually-verified PNGs on fresh
real-CI runs (>=2 !testme). Cosmetics-never-block and secret-safety guardrails
binding. Also: temporary hourly-wake instruction to verify the new limit-wait
system tonight; journal entry.

cc-ci-plan/JOURNAL.md

@@ -386,3 +386,16 @@ cc-ci-orchestrator-vm, repointed .orchestrator-session-id (old → .bak). Loops
 limit-stall window 07:51–08:03 via watchdog kill/reboot/nudge — resilience layer worked as designed.
 Open for operator: review/merge immich PR#2 + plausible PR#3 (still green, unmerged); stale
 session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private.
+
+## 2026-06-11 ~01:15 — phase `shot` queued; limit-system night watch
+- Operator requested a follow-on phase: audit + repair the per-recipe CI screenshot
+  (badge/card) across ALL enrolled recipes. Plan written:
+  cc-ci-plan/plan-phase-shot-screenshots.md, queued AFTER rcust in .phases-spec
+  (rcust;shot) — watchdog auto-advances on rcust `## DONE`.
+- Pre-audit evidence (last ~120 runs): plausible screenshot=null on every run;
+  immich/lasuite-meet/cryptpad (+flaky n8n) produce byte-identical ~4.8KB PNGs =
+  suspected blank SPA frames; ghost/mattermost/discourse/etc healthy.
+- Hourly wakes tonight: TEMPORARY line added to ai-progress-monitor-prompt.txt — verify
+  the new limit-wait system (d6e1a70/2e1ab8d) on each wake; remove the line 06-11 daytime.
+- Orchestrator renamed cc-ci-orchestrator (was -vm); stale Jun01 squatter killed;
+  watchdog bounced twice tonight (limit patch, then hourly-wake-during-limit fallback).