And describing it as a Merkle-style tree conveys additional implementation about the implementation - presumably the tree stores the hash ("computed from all of its source files and inputs") which just saying "it's a DAG" doesn't tell you.

Or just avoid the fancy names and call it what it is: they walk the dependency graph to identify build targets that have a changed dependency.