MarmotOutboundDao.promote and demote commit the room's admin list through
the publish gate, built from the list the group holds when the commit is
staged. AdminGovernance holds the rules once: the library's permissions,
plus that a promoted account holds a leaf, and that a keyed room's admins
are changed by none of this -- they need the group's signature and a
share of its key, which are not built.
Removing an admin now takes them off the admin list first and removes
them when that commit is confirmed, chained by MarmotEngine.afterConfirmed.
A bare Remove left their key on the list, so inviting them back made them
an admin again with nobody having said so.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>