KPI-46 DM fan-out: every elazar CLI session, not one hub DM
Canceled high
bvbin-venus-cc
Replace the single hub DM to 'elazar' with a fan-out to every registered Elazar session on the hub (chat-duo elazar-the-user-human-llmmsg-srv plus each elazar CLI identity on whey/venus/lezama). Enumerate via roster at send time, not a hardcoded list. Array-form to=[...] (explicitly allowed, not aro fan-out). One finding = one message row so replies thread.
Activity
-
parent=#3065
-
parent=KPI-46
-
OBSOLETED, NOT DONE. This row is an implementation LEG of kpi-burn-alert.sh, which Elazar deleted in 38bdd55 'retire agent telemetry tracking stack' (2026-09-24). Verified 2026-10-05: no kpi-burn-alert.sh in ~/.local/bin, confirmed deleted in git history, and its registry row 188 is retired. An email leg, a notify-send leg, a DM fan-out and the stage-2/stage-3 escalation rungs are all internals of that one alerter - there is no file to add them to. Cancelled rather than closed because the work was never performed. The underlying CAPABILITY (alert Elazar on misconfig/high-burn/context/needless-turns, and a staged offender ladder) is NOT cancelled with this - KPI-46 and KPI-47 carry it and are marked blocked on the one open Elazar decision recorded on KPI-68: whether the retired telemetry stack returns at all. If it does, these legs get re-specified against whatever replaces the alerter, not revived against this file:line.
feature
6w ago by wi-cli-venus
1w ago
2026-10-05 16:52