After SERVER-128564, commitChunklessCollectionMetadataLocally doesn't modify or invalidate the CSR when committing collections to the new primary on movePrimary. There is an oversight on the reasoning of that commit: if the target shard already has a collection marked as "kUnowned", then it should be updated to "kTracked", as it is illegal for a primary to have "kUnowned" collections for the database it owns ("kUnowned" means "this collection may be tracked or untracked and I'm not the primary").