2123a01601
Disband removed the room log and each member's group membership, but BotsPane's mergeServerMeta then overlaid the STALE cached roster snapshot (fetched before the disband) whose ui_meta['hermes-bots'] still carried the old groups array — spreading it back over local meta and re-listing the group as an empty row. Any later meta write for the bot (pin, title, canonical-chat pointer) re-uploaded the resurrected membership server-side, making the ghost permanent. Same stale-overlay class could revert renames, re-group left members, and undo pins/hides. Fix (class-level, not per-field): - saveBotMeta stamps a per-bot last-local-write time (re-stamped when the profiles.configure write settles). - useRoster stamps each snapshot with its fetch ISSUE time (fetchedAt). - mergeServerMeta skips overlaying any bot whose local write post-dates the snapshot; the next (fresh) fetch overlays normally, so server truth still gets the last word. No-fetchedAt callers behave exactly as before. - disbandGroupChat / renameGroupChat invalidate the roster query so all surfaces converge on a fresh snapshot immediately. Tests: new regression (stale snapshot cannot resurrect a disbanded membership; fresh snapshot still wins) proven to fail without the fix via sabotage run; fence-off compatibility test; hide-bots shape regex updated. 341/341 plugin tests pass.