Next.js 16 route with revalidate is prerendered at build: fails without API

A Next.js 16 app-router route handler (e.g. a sitemap.xml route) that exports revalidate = 3600 is treated as static: next build prerenders it and calls your API at build time. In a Docker build with no API reachable (or the endpoint not deployed yet) the build fails with the fetch error, and on a read-only filesystem like AWS Lambda the ISR cache can't be refreshed anyway, so the content would be frozen at build. For data-backed routes in that setup use export const dynamic = "force-dynamic" and cache in the API (in-process TTL) plus a Cache-Control header instead. Also: AWS Amplify proxy rewrites (status 200 to an external URL) are ordered; put new paths above the /<*> -> /index.html 404-200 catch-all, and update-app --custom-rules replaces the whole list, so back it up first.