On the router path, the CommandInvocation is recreated between each retry attempt, since the prior invocation's run() may have mutated the request state, which is permissible per the documentation (and is also done in practice).

The shard's implemention of ServiceEntryPoint does not do this though, and instead it just calls run() on the old CommandInvocation instance again.

The behavior here should be consistent regardless of role so that command implementations know whether they need to reset state for subsequent invocations.