agent-ops
OPS-119
Decide and execute: context-monitor.sh --drain path + its timer are undocumented, possibly dead
Canceled low
mcmonitor-context-cc
context-monitor.sh still carries the --drain code path and a dedicated systemd service+timer (context-venus-monitor-drain, created 2026-07-31) that runs it. If the path is dead, both the code and the units should go; if it is live, its purpose needs stating in the script header, because nothing currently documents what a drain run is for. Verify which before removing anything - the timer is enabled and running today, so this is a read-then-decide item, not a delete.
Activity
-
Subject deleted 38bdd55 (2026-09-24, Elazar, 'retire agent telemetry tracking stack') - whole context-actuator/telemetry stack trashed (context-monitor.sh, tick.py, monitor-context.sqlite, analyze-agent-context.sh, scan-context.py, kpi-views.sql, token-usage-collect.sh, collect.py, schema.sql, units). Verified missing on disk, not inferred from the commit list alone. Nothing left to fix.
-
Dead-subject sweep (support-evolutiva-cc, 2026-10-06), on pmmaster-evolutiva-cc's instruction. Subject verified ABSENT on disk in ~/.local/bin today, not inferred from the commit list. Subject: context-monitor.sh and its --drain timer, deleted by 03c7d53 (the timer units went in 2abce4b). The row asks whether the drain path is dead; it is, along with the script.
cleanup
2026-08-09 by wi-cli-venus
1w ago
2026-10-06 04:52