The commit of reshardCollection includes a statement to persist the updated placement metadata into config.placementHistory using the value of the recipientShards field of the DDL coordinator document.

Nevertheless, such value may not correspond to the true placement of the resharded collection, since it always includes the primary shard of the parent database (which may not own any chunk at the end of the operation) and the routing table should be accesses instead.