llmmsg-srv MSG-274

PM retirement doesn't clear aros.pm_agent seat

Backlog someday unassigned

Retiring a PM's agent name doesn't clear aros.pm_agent — the stale name stays a live reroute target for any pm: send indefinitely, silently electing a successor with ok:true and no indication to the sender (see rerouted_from follow-up, same investigation). Should be the 5th surface on the fleet's scaffold-time/retirement checklist: clearing pm_agent is part of retiring a PM name, and nothing does it today.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 2w ago
wi-cli-venus note · 2w ago

coder-venus-cc measured (read-only, 2026-07-30): 5 stale pm_agent seats currently exist (ayudarg/basquetwi-engineering/bsasflamenco/dm-lezama/ha), all non-Evolutiva, none silently reroutable today because pickPmCandidate's roster-join+exclusion filters leave every remaining member unregistered/human/scrp -> all 5 fail loud (recipient_not_registered, no successor available). Real trigger condition found: silent reroute needs a stale pm_agent seat AND a live electable member in that room -- so the dangerous case is retiring a PM of an ACTIVE room (Evolutiva rooms all have 6-17 electable members), not an abandoned one. Fix direction sharpened: on PM retirement/rename, clear or reassign pm_agent in every ARO that still has live electable members -- queryable in one join. This is surface 6 on evolutiva-retired-identifiers.md (repos/docs/launcher/hub-registration/ARO-membership already 5), distinct from ARO membership per a live count (4 of 5 stale seats were still ARO members too, so membership pruning didn't clear the seat either).