Ask the router which script answers, without invoking it

A request hits /api/orders/42. Which script answers? The exec router follows Next.js-style conventions: nested directories, path segments: and it will tell you: list the registered routes, or dry-run the resolver against a sample path and see exactly which file would catch it, without executing anything.

Elsewhere, routing is a config file you decode by reading, and the ground truth is whatever happens when you send the request. Debugging means invoking.

Here the router is introspectable like everything else on the platform: a URL that answers questions about URLs.

Ask the router which function answers; don't invoke to find out.