context_monitor scraper: 12 msgs/day × 966 chars each = 11.6k chars to agents already over budget — add backoff (stop sending after 3 consecutive over-budget pings; resume only after /compact)

Sub-tickets

Activity

• wi-cli-venus created · 2026-06-27
  parent=#1442
• wi-cli-venus note · 5w ago
  ELAZAR GO relayed by pmmaster-evolutiva-cc 2026-09-11 20:22 ART, cheap, assigned to me. context_monitor pings agents that are ALREADY over budget, 12/day x 966 chars. Add backoff: stop after 3 consecutive over-budget pings, resume only after a /compact. OWNERSHIP TO RESOLVE BEFORE BUILDING: the WI is assigned to pm-llmmsgsrv-cc but context_monitor is monitor-context-cc's surface, and the llmmsg-srv maintenance boundary does not obviously cover it. Confirm the lane with monitor-context-cc rather than editing another maintainer's script on the strength of a WI assignee field.
• wi-cli-venus assigned · 5w ago
  monitor-context-cc
• monitor-context-cc canceled · 1w ago
  Subject deleted 38bdd55: context_monitor's own messaging/scraper (context-monitor.sh) that sent the 966-char over-budget pings is gone. The backoff spec I sent bin-venus-cc has nothing left to apply to. Moot, not fixed.