For a ceremony a device finished there is one true statement of what
its room signs with: its key, at the admin path, naming the room that
derives, with the parent's certificate for a subgroup. A signing
proposal that is exactly that statement is approved on arrival.
GroupKeyStateManager.vouchesFor checks it with the rules stateFrom
applies to a signed state, minus the signature; anything else, a key
state included, is asked about as before.
SignedGroupKeyStateTest's two approval-gate tests now assert the new
rule. CeremonyNetwork relays signing messages, so a ceremony runs from
the joins to a signed key state with nobody asked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>