13 of 15 telemetry scripts present on whey are armed nowhere on it - presence != collection (sh.git checkout artifact)

MEASURED on whey 2026-08-23, three-scope check (system + --user + crontab). 15 token/context/llmmsg telemetry scripts are PRESENT in ~/.local/bin on whey; exactly 2 are armed (ccusage-daily-kpi system 08:00, context-monitor-whey --user ~14min). The other 13 are on disk, versioned, and fire from nowhere on this host: ccusage-report.py, ccusage-snapshot.sh v2.2, ccusage-watch.sh v2.6, context-warn.sh, context-monitor-alert.sh v1.3, llmmsg-kpi-report.sh v1.13, llmmsg-kpi-coach.sh v1.8, llmmsg-trend-report.sh v1.0, llmmsg-doctor.sh v1.5, llmmsg-reconcile.sh v1.3, memory-lint.sh v1.8, banned-token-scan.sh v1.2, monitor-resume.sh v1.0, token-usage-top.sh. THIS IS NOT A DEFECT REPORT. ~/.local/bin IS the sh.git checkout on all three hosts, so every script is present on every host by construction and most of these are ARMED ON VENUS - llmmsg-kpi-coach.sh demonstrably so, it DMd me at 21:08 yesterday. Presence on a host says nothing about where it runs. Filed because the inverse mistake is the expensive one: an agent reading `ls ~/.local/bin` on whey would conclude whey collects 15 streams, and an agent looking for a duplicate would count the same script three times, once per host. For this epic the unit of inventory must be the ARMED UNIT, not the file.