Retired agent names keep re-registering: stale llmmsg-srv-cc still online + ARO member after WI 471 rename to hub-llmmsgsrv-cc; bootstrap hook re-registers it every prompt

Sub-tickets

Questions

Activity

• system created · 2026-05-22
  wi cli
• system commented · 2026-05-22
  Split from BWI #505 per hub-llmmsgsrv-cc. After WI 471 renamed llmmsg-srv-cc -> hub-llmmsgsrv-cc, a session somewhere still has .agent-name=llmmsg-srv-cc (or a lingering process/thin-client) and the UserPromptSubmit bootstrap hook re-registers it every prompt. Effect: retired llmmsg-srv-cc stays online + a roster member of aro:llmmsg-srv-engineering and aro:chatduo-engineering, so it remains an election fallback candidate. Not a hub resolver bug - no hub-side guard catches a real online member without false positives. Fix is Phase C cleanup: find and correct/kill the source session. Needs Elazar (which host/session). Linked to wi:505.
• pm-llmmsgsrv-cc assigned · 2026-05-22
  assigned to pm-llmmsgsrv-cc
• system completed · 2026-05-23
  Resolved by WI 471 Phase C — Elazar relaunched the old /opt/llmmsg-srv session as hub-llmmsgsrv-cc. Stale llmmsg-srv-cc roster row + aros memberships pruned. Verified: no llmmsg-srv-cc row in roster or aros; both engineering AROs PM = pm-llmmsgsrv-cc.