cc-context-monitor: fix silent dedup + add process-not-in-roster alert

Sub-tickets

Questions

Activity

• system created · 2026-05-23
  wi cli
• system commented · 2026-05-23
  Two failure modes exposed 2026-05-23: (1) dedup M4 silences re-DM at 1/day even for 3x-over agents — 5 venus agents sat bloated+invisible for 50+ min with no re-alert. Fix: relax dedup threshold, re-DM every cycle when >2x over budget. (2) No alert for 'process running but not in hub roster' (Mode A silent hub-loss) — agents on old shim silently fail to register; monitor never detects them. Fix: cc-context-monitor should cross-check pgrep claude vs hub roster and alert on unregistered running sessions.
• system commented · 2026-05-23
  scope/b: LLMMSG_AGENT env var set by ccs.sh on every session — readable via /proc/<pid>/environ. Also .agent-name in cwd. Deterministic pid→agent-name map. 30-min job.
• system statusChanged · 2026-05-23
  PM go-ahead per tag mphyfpgl41xm; two-commit split per one-bump rule
• system completed · 2026-05-23
  shipped cc-context-monitor.sh v2.10 in two commits per one-bump rule: v2.9 (5ae0b31) dedup-relax >=2x bypass + [SEVERE] tag; v2.10 (3af9d51) pgrep-vs-roster cross-check via hoisted /roster + pid_agents map + state['unregistered'] dedup. Distribution: nw-venus-cc + nw-lezama-cc per standing sh-git-sync.