At present, the movePrimary command will cause a single-collection change stream to be invalidated, because the operation ends by dropping the collection on the original shard. Instead, the stream should be able to continue reading events from the collection after it has been moved to the new shard. This will require the drop event to be marked as fromMigrate:true.

Additionally, the UUID of the collection on the new shard will be different than on the original (see this comment and SERVER-32847). This should be changed so that the UUID remains consistent throughout.