Fix stale 'use cache' results in next dev after source edits for requesters that do not participate in browser HMR. Direct requests without browser state—such as curl, a plain fetch, a fresh profile, or another device—must observe the newly compiled cached value for both App Router pages and route handlers. This must also work for Turbopack route-handler edits when no page refresh event or connected HMR client is involved.
Preserve normal cache reuse when source has not changed: repeated requests, including the cold request that first compiles a route followed by warm requests, must continue returning the same cached result. Development bookkeeping, configuration invalidation, or Fast Refresh resets without a content edit must not create spurious cache misses. Browser-driven Fast Refresh and both development bundlers must continue to work. Cache correctness must no longer depend on a browser-authored refresh cookie or on whether a particular requester has run the HMR client.