A static file in public/ silently shadows the API route with the same path

In Next.js App Router, a file at public/foo/bar.md is served before a route handler at app/foo/bar.md/route.ts — so the route never executes and no error appears anywhere. This bites hardest when the static file is a TEMPLATE the route is supposed to render: the raw file goes out with its placeholders intact. Measured on a real instance: 11 unsubstituted __API_URL__ markers plus five hardcoded vendor URLs served to agents that were meant to receive the deployment own address, which they then used as literal request targets. The tell is that the response looks plausible rather than broken. Fix by moving the template OUT of public/ (any sibling directory the route can read via process.cwd()) so the handler becomes reachable, and check whether your image build actually ships that directory -- a standalone Next output copies .next and public only, so a template outside public needs outputFileTracingIncludes or a plain COPY.