When comparing two documents, webMethods Designer should not just ignore differences in 'child' documents

A disconcerting finding was reported in SI-569377. When comparing a document between two IS instances, webMethods Designer simply ignores any differences between any 'child' documents included by reference by the parent document being compared. If a child document is different on the two IS instances, the two parent documents are declared to be identical!

The following justification was provided in SI-569377. It states that because documents can be recursive, showing differences in referenced child document is un-intuitive. 
-- 
Thanks for your patience, as checked with the RnD, the reported use case ( changes differences cannot be found on the parent document type) is as designed.

As designed, while comparing the documents, the changes of the child reference documents will not be shown in the parent document compare functionality. User needs to use child document compare to get the differences from different versions of the same package deployed in different environment servers.

Alternatively, user can also use the folder level compare to identify the differences. This is as designed as technically the documents can be recursive and so showing all child reference document changes would not be user intuitive.
-- 

This explanation and refusal to fix does not make sense. webMethods is a visual development tool. That means webMethods developers cannot access alternative diff/merge/patch tools but depend on functionality offered by webMethods Designer. A properly functioning Designer compare tool is essential for a proper webMethods development process. Failing to consider referenced data structures in the comparison process has already mislead developers.