You are right, and it happens that the output looks decent.

Code idioms, or patterns if you will, is largely our solution.

We have small pattern/[pattern].md files througout the code base where we explain how certain things should be done.

In this case, the migration was a normalization to the specific pattern specified in the pattern file for the endpoints.

Semantics was not changed and the transform was straight forward. Just not task I would be able to justify spending time on from a business perspective.

Now, the more patterns you have, and the more your code base adheres to these patterns, the easier you can verify the code (as you recognize the patterns) and the easier you cal call out faulty code.

It is easier to hear an abnormality in music than in atmospheric noise. It is the same with code.