validateCollectionMetadata in metadata_consistency_util.cpp currently only validates chunk domain coverage (via validateChunksDomainCoverage), which checks that the union of chunk ranges is consistent between the shard catalog and the global catalog. It does not compare individual chunks 1:1 or validate per-chunk fields.

Once split and merge operations are authoritative through the shard catalog, the chunk sets on both sides should be identical.