Currently this could only happen (barring weird user behavior such as manually attaching a shard version to a command) via a command which is improperly protected accessing sharding components. We should ensure that commands which access sharding components are correctly gated in a way that doesn't require every sharding command to start with a check to the cluster role and/or a call to assertCanAcceptShardedCommands.