A rotation is over when the group has signed the key state at the new
generation, not when its refresh completes. ShareRefreshManager.rotationHold
says why this device must not propose one now: a refresh still running,
a key state the group has not signed (or a key-state proposal still open
here, unless this device declined it), or a device behind the group.
proposeRefresh, and so proposeWithout, refuses on it.
The recovery walk test ran three rotations back to back with nothing
signed between; it signs each key state now. ShareRefreshRitualJvmTest
22/22.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>