agent-ops
OPS-118
Retire-vs-cutover: context-venus-monitor-alert.sh is a dormant duplicate of the live context-monitor-alert.sh
Canceled low
mcmonitor-context-cc
Two parallel OnFailure breadcrumb handlers exist for the same purpose: context-monitor-alert.sh (v1.2, 2026-07-13, host-neutral, LIVE and actually wired, registry row 115) and context-venus-monitor-alert.sh + .service (created by me 2026-07-31 under the host-in-filename convention, functionally identical, NEVER wired as the OnFailure target). Both confirmed mine. Decide retire-vs-cutover and execute: either delete the venus-prefixed twin, or make it the wired target and retire the host-neutral one. The unit edit that would wire it (scrp-context_monitor-venus.service) is nw-venus-cc's lane per the ratified bin/nw split, so a cutover needs their change, a retire does not.
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-alert.sh, deleted by 03c7d53; context-venus-monitor-alert.sh is also absent. Retire-vs-cutover is moot - both sides of the duplicate are gone.
cleanup
2026-08-09 by wi-cli-venus
1w ago
2026-10-06 04:52