With OnlineMovePrimaryLifecycle enabled, the recipient manages its own critical section instead of relying on commands sent by the coordinator. The ShardsvrMovePrimaryExitCriticalSectionCommand clears the database info on the recipient node before releasing the critical section, but the MovePrimaryRecipient currently does not do this.

A possible fix is on the test branch here.