If a 3 node cluster is brough down with "shutdown cluster" the state files are created in <node>/data
After restart it successfully and shutdown all nodes individually the expectation is that atart one node will work.
But as the files are still there there is the
Caused by: java.lang.IllegalArgumentException: Command does not have a topology id
error until all nodes are back.

Also if starting a NEW node the state is messed up as well.

The expected behavior here, as the cluster has been scaled down to 0 (one by one) is that it must be possible to start one node as the 'new' cluster in the same way as if there was no "shutdown cluster" before.
Note if two nodes are stopped the last node is consistent and contains all entries (as expected) and is working properly. After restarting it (which can be a long period after the others) the behavior is similar to a cluster-shutdown
which is completely unexpected (as the other nodes might be deleted completely on purpose)