After a rename both collections are marked as authoritative and will trigger a set of extra validations for authoritatively sharded collections.

This however, races with migrations as those will trigger recovery at the start of the migration on the recipient. At that precise moment if the collection doesn't exist on the shard it will be marked as unsharded and untracked even if globally it is sharded as part of authoritative recovery. The valid filtering metadata is only installed at the end once the critical section has been acquired.

If a metadata consistency checks happens between those two moments it will fail with an inconsistency.