The API you wish you'd shipped, layered over the one you did

Your public API grew for six years and it shows: inconsistent casing, three pagination styles, endpoints nobody would design today. A rewrite is quoted in quarters.

Instead you put a hoody-exec script in front. Clients call the API you wish you'd shipped: clean paths, one pagination style, sane errors. The script translates each request into whatever the old backend actually expects, calls it, and reshapes the response on the way out. The legacy code doesn't change. It doesn't even know.

Deprecations become translation rules. New endpoints appear as files. When you eventually do rewrite the backend, clients notice nothing, because they were never talking to it.

The redesign ships as a layer, not a rewrite.