yang.data.api.schema.tree.spi.MutableTreeNode acts as a lazy intermediary between ModificationApplyOperation and a backing Map. Its addChild() and removeChild() hide lifecycle events, making it impossible to discern when a child was replaced by addChild() and what child was removed by removeChild().

Update these methods (renaming addChild() to putChild()) to match map semantics.