So dir is not shipped due to conflict with built-ins, echo and rmdir are shipped despite conflicts, and sort is deemed not to have a conflict? What is the logic?
My guess is that some commands are compatible because they behave the same on both systems when used without command line options, and the implementation can distinguish between DOS and Unix options.
AI said to do it.
As hex4def6 said, the idea was that DOS command conflicts are not a good idea, while overriding PowerShell builtins in interactive sessions (PSReadLine) is acceptable, if not a good idea. We open-sourced DOS sort and published a port of the DOS find command. The suite then dispatches to the GNU/DOS variant based on heuristics.
I think if it conflicts with a CMD command it's not shipped, but if it conflicts with a powershell command it's ok.
No idea, this is broken at start, I would expect at least a reasoning on how they expect to improve the mess going forward.
Otherwise just don't do it, if it is going to be a mess to work with.