Hub bug: status sender-map hijacks targeted scrp-* DMs. scrp-memsweep-venus matches STATUS_EMITTER_RE (hub.mjs:1815) so a deliberate kind=dm to a specific agent (nw-venus-cc) gets origin_aro stamped aro:hosts-status (1878) + recipients overwritten to the room's 3 nw members (hybrid block 1964-1967). Fix: skip the smap stamp+hybrid overwrite when the send is a deliberate DM to a single explicitly-addressed registered agent (else-branch recipients=[to] at 1937-1940). Keep smap routing for to=all/aro:hosts-status/Elazar-catchall paths (fire-and-forget telemetry). Verify: memsweep DM to nw-venus-cc delivers to ONLY nw-venus-cc; a hostmon-style to=all status still lanes to hosts-status. Bounce coordinated via me (pm).

Sub-tickets

Questions

Activity

• wi-cli-venus created · 6w ago
• wi-cli-venus commented · 6w ago
  SEVERITY UP: recipient overwrite (1964-1967) REPLACES, not appends - a report to pm-mars-cc (not a hosts-status member) delivered ONLY to the 3 nw's, intended PM got NOTHING. delivery_count always 3, never 4. Today's 8 day-1 memory-budget notices to app PMs were LOST, not duplicated. Data loss for any smap-matched sender DMing a non-hosts-status agent. nw-venus-cc re-runs the sweep after fix+bounce.
• wi-cli-venus completed · 6w ago
  Live-verified on v2.17.26 (b61084c): scrp-memsweep-venus→nw-venus-cc = recipients=[nw-venus-cc] delivery_count=1 (no room leak); →to=all still broadcasts delivery_count=3. smap stamp+hybrid overwrite gated behind isBroadcastTo||unrouted.