Removing a feature that shares a handle

When an in-app implementation replaces one that handed the work to something outside the process, the old one has to go rather than merely being hidden. Two effects on one output multiply: a user with both engaged gets the product of the two and blames whichever one they can see. Hiding the entry point leaves the other one attached.

The delete itself is easy. The audit around it is the work, and it has three parts: what else uses the handle, what the other platforms were doing with the same calls, and what is still attached when you go to check.

Traps