The automatic ceremony lets a device sign, without asking its owner, the one key state that can be true for a ceremony it finished (GroupKeyStateManager.vouchesFor). Its seventh condition -- no state for the room already signed here -- was what kept a share rotation's key state out, and only in rooms that already had one. An eighth makes it explicit: a state naming a share generation or a member binding says more than the ceremony did, and its owner is asked. Found by ShareRefreshRitualJvmTest after the merge: its devices hold no first state, and the generation-1 state signed itself. jvmTest 1229/1229, compileDebugKotlinAndroid, audits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>