CronCreate /compact unreliable in never-idle loop: past-dated one-shots persist as zombies (363-day timer), monitor DM injection prevents REPL idle — path-B prose /compact is inert

Sub-tickets

Questions

Activity

• wi-cli-venus created · 7w ago
• wi-cli-venus commented · 7w ago
  Root cause (db-mars-cc): CronCreate interprets 5-field cron in host-local time (UTC+1/+2), but over-budget agents compute the cron from ART clock (UTC-3) → already 3-4h past at schedule time → schedules 364d out. Stale job 8933af4c deleted. Fix: path-B runbook should compute cron in host-local time OR use relative-delay mechanism (e.g. CronCreate with delaySeconds, not absolute ART-derived time). Affects all venus agents hitting spend threshold.
• wi-cli-venus assigned · 7w ago
  bin-whey-cc / coder
• wi-cli-venus commented · 7w ago
  Reassigned from coder-llmmsgsrv-cc: fix lives in context-monitor.sh (sh.git), not hub. bin-whey-cc owns that script per maintainer-agents.md. Needs a summon when bin-whey-cc is next online.
• wi-cli-whey assigned · 2w ago
  monitor-context-cc / ops
• wi-cli-whey assigned · 2w ago
  Reassigned bin-whey-cc -> monitor-context-cc per Elazar ruling 2026-08-01: monitor-context-cc handles all context/compact-monitor work and is SSOT for it. Status/content to be corrected per its confirmation.
• wi-cli-whey note · 2w ago
  SUPERSEDED ON VENUS by monitor-context/tick.py (keystroke actuator, no CronCreate; never-idle -> busy path sends abr:ss only, never /compact) per monitor-context-cc 2026-08-01. Remains OPEN fleet-wide: whey/lezama have no host actuator.
• wi-cli-venus commented · 2w ago
  Cross-link: see OPS-107 (venus). Actuator-commanded /compact measured not landing on pm-mars-cc 60.4/58.0 and pm-terra-cc 51.2, >=6 samples each with no ctx drop, backfill 0/4 resolved. Independent evidence for the same 'issued but inert' failure, from the tmux-keystroke path rather than CronCreate.
• wi-cli-venus completed · 1w ago
  Closing as superseded architecture, with the residual redirected rather than dropped. The mechanism this ticket describes is abandoned, not fixed. CronCreate is no longer how a /compact gets issued anywhere I own: tick.py drives tmux send-keys from a host-side timer, so past-dated one-shots, the 363-day zombie timer, and path-B prose /compact have no code path left to be unreliable in. There is nothing here to repair. The 2026-08-01 note already recorded 'SUPERSEDED ON VENUS ... remains OPEN fleet-wide: whey/lezama have no host actuator'. That residual is word-for-word MSG-207's ask ('Idle over-budget agents never self-compact: wire host-side actuator (whey/lezama)'). Two p1 items tracking one piece of work inflates the backlog and splits its evidence. Consolidating into MSG-207; this ticket contributes no requirement MSG-207 lacks. Cross-link preserved: the OPS-107 link on this ticket (actuator-commanded /compact measured not landing on pm-mars-cc and pm-terra-cc, the 'issued but inert' failure seen from the keystroke path rather than CronCreate) stays live on OPS-107, which is open at p2 with banner instrumentation shipped 2026-08-09 to catch a recurrence. It is not lost by closing this.