Host-status rooms + hub catch-all routing: zero untagged DMs to Elazar (4b hub-route)

Sub-tickets

Questions

Activity

• system created · 2026-06-05
  wi cli
• system note · 2026-06-05
  SPEC (Elazar-decided). Two streams. ROOMS (coder-chatduo-cc): create aro:whey-status / aro:lezama-status / aro:venus-status. Pin all 3 at TOP of ARO list in BOTH clients (GTK + web), faint color tint vs normal rooms. Elazar joins all 3. HUB ROUTING 4b (hub-llmmsgsrv-cc): hub rewrites destination by SENDER-MAP, not keywords. - cc-context-monitor-<host> + hostmon-<host> -> aro:<host>-status (origin_aro stamped hub-side). - CATCH-ALL: any send to=elazar-* with NO resolvable origin_aro -> hub rewrites into default sink aro:whey-status (hub host) + marker tag like [unrouted-default]. NEVER reject, NEVER leave as a bare Direct-pane DM. Scripts dont read replies so a bounce = a dropped alert. - Agent senders ALSO get a non-blocking nudge reply (tag origin_aro next time) - educational, but the message STILL lands in the room. Route-always, nudge-if-agent. GOAL: Elazar receives ZERO untagged DMs; every message renders in a lane. Decided: 4b over 4a (source-tag) for chokepoint enforcement independent of sender discipline. Default sink = whey-status (PM pick, Elazar can override).
• system completed · 2026-06-05
  Shipped + verified. hub 2.9.19 (1d86734/f4f20b8): sender-map cc-context-monitor|hostmon-<host> -> origin_aro=aro:<host>-status; catch-all untagged-DM-to-Elazar -> aro:whey-status + [unrouted-default]; hybrid fan-out-if-members-else-stamped-DM (zero drop); agent nudge; hub-internal alerts included. chat-duo-web 0.5.18 + GTK 1.20.7 (ccfa4b3): 3 status lanes pinned top + tinted. Lanes render on first stamped alert; Elazar-join only needed for multi-subscriber fan-out.