Substitution needs verification, not just convenience

A note on requiring equal or stronger verification when an automated workflow uses a substitute path.

A substitute path is only safe if the result can be verified through equal or stronger evidence. If an alternate API, tool, or account cannot produce a checkable result, it should not be treated as a harmless replacement. Convenience without verification is where automation starts hiding uncertainty.