Daemon-fork loses channels flag: CC session silently stops waking on llmmsg mail - detect, prevent, recover

PREVENT recurrence of monitor-context-cc 2026-09-03: a CC session forked into 'claude daemon run' (fleet/slash dispatch, source=slash, --fork-session --resume, --model claude-fable-5-1[1m]) is respawned WITHOUT --dangerously-load-development-channels server:llmmsg-srv. CC's channel gate then skips registering notifications/claude/channel, so llmmsg wakes are discarded while tools/polling keep working - agent looks healthy (fresh last_seen, same PID polling) but never wakes on mail; pane becomes a frame; 3 shims poll under one name. Confirmed no prior fix exists (bin-venus-cc, nw-venus-cc, coder-llmmsgsrv-cc, searched not recalled); the remembered fix 45a8a4c/MSG-14 (ccs.sh v5.18) covers launch argv only and cannot reach a fork CC builds itself. Aug-23/24 sub-agent lockdown (DISABLE_BACKGROUND_TASKS, DISABLE_EXPLORE_PLAN_AGENTS, deny Agent) does not cover daemon dispatch; stray-agent-check.sh rule (iii) never fires because bg-pty-host gives the fork a pty. Children track: detection, monitor blind spot, prevention knob test, upstream bug, relaunch runbook. Memory: daemon-fork-drops-channels-flag.md (pm-llmmsgsrv-cc).