@warlock.js/web 5.2.4 → 5.3.1

package/esm/server/framework-default-not-found-stylesheet.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"framework-default-not-found-stylesheet.mjs","names":[],"sources":["../../../../../../../web/src/server/framework-default-not-found-stylesheet.ts"],"sourcesContent":["/**\n * The framework fallback 404 document's stylesheet, duplicated here as a\n * plain string constant.\n *\n * `framework-default-not-found.css` remains the source of truth for this\n * stylesheet's content — this file is a build-time necessity, not a second\n * design surface. The production server build refuses to compile\n * static-asset imports (`?raw`, `?url`, `import.meta.url`) in the page\n * graph, and says so in its own diagnostic: see the `REMEDY` text in\n * `../build/generate-pages-barrel.ts`. `not-found-page.ts` is part of that\n * server build, so it cannot import the `.css` file directly and must read\n * its text from a plain module instead.\n *\n * `not-found-page-stylesheet.spec.ts` asserts this constant stays\n * byte-identical to the `.css` file, so a future edit to one cannot silently\n * drift from the other.\n */\nexport const FRAMEWORK_DEFAULT_NOT_FOUND_STYLESHEET = `:root {\n  color-scheme: light dark;\n}\n\n* {\n  box-sizing: border-box;\n}\n\nbody {\n  margin: 0;\n  min-block-size: 100vh;\n  display: grid;\n  place-items: center;\n  padding-block: 2rem;\n  padding-inline: 1.5rem;\n  background: #fafafa;\n  color: #18181b;\n  font-family: system-ui, sans-serif;\n}\n\nmain {\n  inline-size: min(100%, 34rem);\n  text-align: center;\n}\n\n.rule {\n  block-size: 1px;\n  inline-size: 3rem;\n  margin-block: 0 1.5rem;\n  margin-inline: auto;\n  background: #facc15;\n}\n\nh1 {\n  margin: 0;\n  font-size: clamp(4rem, 16vw, 7rem);\n  font-weight: 700;\n  letter-spacing: -0.06em;\n  line-height: 1;\n}\n\np {\n  margin: 1.25rem 0 0;\n  color: #52525b;\n  font-size: 1rem;\n  line-height: 1.5;\n}\n\na {\n  display: inline-block;\n  margin-block-start: 1.5rem;\n  color: inherit;\n  text-underline-offset: 0.2em;\n}\n\na:focus-visible {\n  outline: 2px solid #facc15;\n  outline-offset: 4px;\n}\n\n@media (prefers-color-scheme: dark) {\n  body {\n    background: #18181b;\n    color: #fafafa;\n  }\n\n  p {\n    color: #d4d4d8;\n  }\n}\n`;\n\n/**\n * Build the `data:text/css` URL the fallback document's `<link>` points at.\n *\n * Base64-encoded so the CSS's own characters (`\"`, `<`, newlines) never need\n * escaping for use inside an HTML attribute.\n */\nexport function buildFrameworkDefaultNotFoundStylesheetUrl(): string {\n  const base64 = Buffer.from(FRAMEWORK_DEFAULT_NOT_FOUND_STYLESHEET, \"utf8\").toString(\"base64\");\n\n  return `data:text/css;base64,${base64}`;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;AAiBA,MAAa,yCAAyC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8EtD,SAAgB,6CAAqD;CAGnE,OAAO,wBAFQ,OAAO,KAAK,wCAAwC,MAAM,CAAC,CAAC,SAAS,QAEhD;AACtC"}

package/esm/server/install-page-routes-from-manifest.mjs

@@ -2,9 +2,9 @@ import { publishRouteTable } from "../routing/route-table.mjs";
 import { isLoaderShortCircuit } from "./settle-page-response.mjs";
 import { createPageModuleLoader } from "./create-page-module-loader.mjs";
 import { composeRoutePath } from "../routing/compose-route-path.mjs";
-import { deriveFilesystemRouteName, deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
+import { deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
 import { NestedLayoutsNotSupportedError, selectPageLayout } from "../routing/layout-policy.mjs";
-import { canonicalizeRouteExport, deriveFallbackRouteName } from "../routing/route-identity.mjs";
+import { canonicalizeRouteExport, resolvePageRouteCache, resolvePageRouteName } from "../routing/route-identity.mjs";
 import { createPageRouteHandler } from "./create-page-route-handler.mjs";
 import { productionStylesheetUrls } from "./stylesheet-urls.mjs";
 import { DuplicateNotFoundPageError, NOT_FOUND_ROUTE_NAME, NOT_FOUND_ROUTE_PATH, NotFoundPageDeclaresRouteError, createNotFoundRouteHandler, isNotFoundPageFile } from "./not-found-page.mjs";
@@ -48,21 +48,16 @@ import { Response } from "@warlock.js/core";
 function webRelativeSourceFile(sourceFile) {
 	return sourceFile.split("/").slice(2).join("/");
 }
+/** Exported for `../routing/route-name-parity.spec.ts`, which proves this and dev's `resolvePageRouteIdentity` agree. */
 function resolveRoute(routeExport, sourceFile) {
-	if (routeExport === void 0) {
-		const pageFile = webRelativeSourceFile(sourceFile);
-		return {
-			path: deriveFilesystemRoutePath({ pageFile }),
-			name: deriveFilesystemRouteName(pageFile)
-		};
-	}
-	const canonical = canonicalizeRouteExport(routeExport);
+	const pageFile = webRelativeSourceFile(sourceFile);
+	if (routeExport === void 0) return {
+		path: deriveFilesystemRoutePath({ pageFile }),
+		name: resolvePageRouteName(routeExport, pageFile)
+	};
 	return {
-		path: canonical.path,
-		name: canonical.name ?? deriveFallbackRouteName({
-			routePath: canonical.path,
-			sourceFile
-		})
+		path: canonicalizeRouteExport(routeExport, sourceFile).path,
+		name: resolvePageRouteName(routeExport, pageFile)
 	};
 }
 /**
@@ -154,6 +149,7 @@ function installPageRoutesFromManifest(options) {
 		const { host: layout, prefix: layoutPrefix } = layoutLevelOf(page);
 		const routeExport = page.module.route;
 		const { path: routePath, name } = resolveRoute(routeExport, page.sourceFile);
+		const cache = resolvePageRouteCache(routeExport, page.sourceFile);
 		const effectivePath = routeExport === void 0 ? deriveFilesystemRoutePath({
 			pageFile: webRelativeSourceFile(page.sourceFile),
 			layoutPrefixes: layoutPrefixesOf(page)
@@ -177,7 +173,8 @@ function installPageRoutesFromManifest(options) {
 			loadRegistrationLayouts: () => Promise.resolve(page.layouts.map((layout) => layout.module)),
 			hydrationClientModuleUrl,
 			loadErrorPage,
-			stylesheetUrls
+			stylesheetUrls,
+			cache
 		}), {
 			name,
 			isPage: true

package/esm/server/install-page-routes-from-manifest.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"install-page-routes-from-manifest.mjs","names":[],"sources":["../../../../../../../web/src/server/install-page-routes-from-manifest.ts"],"sourcesContent":["/**\r\n * Page-route registration for a built application.\r\n *\r\n * `installPageRoutes` answers \"which pages exist?\" by walking the filesystem\r\n * and \"what is this module?\" by asking Vite to evaluate it. Neither question\r\n * can be asked of a running production process: there is no `app/` tree beside\r\n * the bundle and no Vite. Both answers were therefore moved to build time — the\r\n * generated `pages.ts` barrel statically imported every page, layout and the\r\n * app root and handed them over as a {@link PageManifest}, and this module\r\n * turns that table into registered routes.\r\n *\r\n * WHAT IS DELIBERATELY IDENTICAL TO DEVELOPMENT: the route a page ends up on,\r\n * and the guards that run before it renders. A page's `route` export and the\r\n * `prefix` and `middleware` exports of EVERY layout on its path are read off the\r\n * module namespaces here, at boot, and composed by the same rules dev composes\r\n * them by ({@link layoutLevelOf}, {@link composeLayoutLevel}) — so the URL a page\r\n * answers on and the chain that guards it are decided by the page's own source\r\n * in both modes, and a build cannot quietly disagree with the dev server about\r\n * either.\r\n *\r\n * WHAT IS DELIBERATELY DIFFERENT: this is synchronous. Every module is already\r\n * in memory, so registration has nothing to await; the loader handed to each\r\n * handler is a lookup over the same table, not an evaluation step.\r\n */\r\nimport { composeRoutePath } from \"../routing/compose-route-path\";\r\nimport { deriveFilesystemRouteName, deriveFilesystemRoutePath } from \"../routing/filesystem-route\";\r\nimport { NestedLayoutsNotSupportedError, selectPageLayout } from \"../routing/layout-policy\";\r\nimport { canonicalizeRouteExport, deriveFallbackRouteName } from \"../routing/route-identity\";\r\nimport { publishRouteTable } from \"../routing/route-table\";\r\nimport { Response, type Router } from \"@warlock.js/core\";\r\nimport { createPageModuleLoader } from \"./create-page-module-loader\";\r\nimport type { ErrorPageModule } from \"./error-page\";\r\nimport {\r\n  createPageRouteHandler,\r\n  type PageRouteHandler,\r\n  type PageRouteHandlerOptions,\r\n} from \"./create-page-route-handler\";\r\nimport type { PipelineLoader, PipelineMiddleware } from \"./execute-page-request\";\nimport { isLoaderShortCircuit } from \"./settle-page-response\";\nimport { productionStylesheetUrls } from \"./stylesheet-urls\";\r\nimport {\r\n  createNotFoundRouteHandler,\r\n  DuplicateNotFoundPageError,\r\n  isNotFoundPageFile,\r\n  NotFoundPageDeclaresRouteError,\r\n  NOT_FOUND_ROUTE_NAME,\r\n  NOT_FOUND_ROUTE_PATH,\r\n  type RegisteredRouteShape,\r\n} from \"./not-found-page\";\r\nimport type { PageManifest, PageManifestLayoutEntry, PageManifestPageEntry } from \"./page-manifest\";\r\n\r\n/** A page declares either a bare path or a path plus an explicit route name. */\r\ntype PageRouteExport = string | { path: string; name?: string };\r\n\r\n/** The only export this module reads off a page module namespace. */\r\ntype PageModuleShape = {\r\n  route?: PageRouteExport;\r\n};\r\n\r\n/** The exports this module reads off a layout module namespace. */\r\ntype LayoutModuleShape = {\r\n  prefix?: string;\r\n  /**\r\n   * The default export — the thing that puts an element in the document, and\r\n   * therefore the ONLY export that decides whether a layout counts against the\r\n   * single-rendering-layout rule (`../routing/layout-policy.ts`). The manifest\r\n   * carries LOADED modules, so this is a fact rather than a guess, exactly as it\r\n   * is in dev (`install-page-routes.ts:145-150`).\r\n   */\r\n  default?: unknown;\r\n  /** The layout's guards, in the order it declared them. */\r\n  middleware?: readonly PipelineMiddleware[];\r\n  loader?: PipelineLoader;\r\n};\r\n\r\n/**\r\n * How a handler is built for one page. Defaults to `createPageRouteHandler`;\r\n * taking it as an input keeps this module's own job — reading the manifest and\r\n * registering routes — provable without a render pipeline behind it.\r\n */\r\nexport type PageRouteHandlerFactory = (options: PageRouteHandlerOptions) => PageRouteHandler;\r\n\r\nexport type InstalledManifestPageRoute = {\r\n  /** The canonical declared route path, before layout-prefix composition. */\r\n  declaredPath: string;\r\n  /** The composed path the route was registered on. */\r\n  path: string;\r\n  /** The resolved route name; shared namespace with API routes. */\r\n  name: string;\r\n  /** The page's manifest `sourceFile`. */\r\n  file: string;\r\n  /** The layout's manifest `sourceFile`, when the page has one. */\r\n  layoutFile: string | undefined;\r\n};\r\n\r\nexport type InstallPageRoutesFromManifestOptions = {\r\n  router: Router;\r\n  /** The table the generated production barrel provided at import time. */\r\n  manifest: PageManifest;\r\n  /** Browser module loaded after the server-rendered application and payload. */\r\n  hydrationClientModuleUrl?: string;\r\n  /**\r\n   * Where the client build wrote its output — `productionStylesheetUrls`'s own\r\n   * `clientDir` argument, forwarded here rather than pre-read into a flat list:\r\n   * each registered handler needs its OWN chain\r\n   * (`[root, ...outer-to-inner matched layouts, page]`, matched by the\r\n   * manifest's own `sourceFile` ids), not one list shared by every page.\r\n   *\r\n   * OPTIONAL for the same reason `PageManifest.clientDir` is: a build that\r\n   * discovered zero pages emits no client bundle, so there is no directory to\r\n   * read stylesheets from — and no page that could need one either.\r\n   */\r\n  clientDir?: string;\r\n  /** Same helper `dev-server.ts` exports — passed in, never imported. */\r\n  createHandler?: PageRouteHandlerFactory;\r\n};\r\n\r\n/**\r\n * `sourceFile`'s path relative to the web root — `src/web/**`, the only page\r\n * root discovery enumerates (`discoverWebRoots`,\r\n * `web/src/build/discover-pages.ts:210-213`). Manifest `sourceFile`s are\r\n * app-root-relative (`\"src/web/...\"`, `page-manifest.ts`'s own doc comment),\r\n * so dropping the first two segments — `<srcDir>`, then the literal `\"web\"` —\r\n * recovers exactly what `deriveFilesystemRoutePath`/`deriveFilesystemRouteName`\r\n * expect: the same value dev computes as `filesystemPageFileFor`\r\n * (`install-page-routes.ts:101-103`).\r\n */\r\nfunction webRelativeSourceFile(sourceFile: string): string {\r\n  return sourceFile.split(\"/\").slice(2).join(\"/\");\r\n}\r\n\r\nfunction resolveRoute(\r\n  routeExport: PageRouteExport | undefined,\r\n  sourceFile: string,\r\n): { path: string; name: string } {\r\n  if (routeExport === undefined) {\r\n    const pageFile = webRelativeSourceFile(sourceFile);\r\n\r\n    return {\r\n      path: deriveFilesystemRoutePath({ pageFile }),\r\n      name: deriveFilesystemRouteName(pageFile),\r\n    };\r\n  }\r\n\r\n  const canonical = canonicalizeRouteExport(routeExport);\r\n\r\n  return {\r\n    path: canonical.path,\r\n    name: canonical.name ?? deriveFallbackRouteName({ routePath: canonical.path, sourceFile }),\r\n  };\r\n}\r\n\r\n/**\r\n * Every layout's declared `prefix`, keyed by its directory relative to the\r\n * web root — the same table dev builds as `LayoutLevel.prefixesByDirectory`\r\n * (`install-page-routes.ts:214-222`) and the one\r\n * {@link deriveFilesystemRoutePath} uses to let a directory's own layout\r\n * rename the URL segment a bare directory name would otherwise contribute.\r\n */\r\nfunction layoutPrefixesOf(page: PageManifestPageEntry): Record<string, string> {\r\n  return Object.fromEntries(\r\n    page.layouts.flatMap((layout) => {\r\n      const prefix = (layout.module as LayoutModuleShape).prefix;\r\n\r\n      if (prefix === undefined) return [];\r\n\r\n      const relative = webRelativeSourceFile(layout.sourceFile);\r\n      const slashIndex = relative.lastIndexOf(\"/\");\r\n      const directory = slashIndex === -1 ? \"\" : relative.slice(0, slashIndex);\r\n\r\n      return [[directory, prefix]];\r\n    }),\r\n  );\r\n}\r\n\r\n/**\r\n * The page's layout LEVEL, resolved from the whole chain the manifest carries\r\n * rather than from the one layout nearest to it — the same resolution dev makes\r\n * (`install-page-routes.ts:138-164`), against loaded modules instead of Vite's.\r\n *\r\n * The manifest carries the FULL chain, outermost first, and the render pipeline\r\n * has exactly one layout slot per page (`execute-page-request.ts`'s\r\n * `PageRouteEntry[\"triple\"]`), so the chain has to be collapsed into one module\r\n * before it reaches a handler. Two things collapse differently and both matter:\r\n *\r\n * - RENDERING is a selection: at most one layout on the chain may render, and\r\n *   the policy picks it. `renders` is read off the loaded module\r\n *   (`typeof module.default !== \"undefined\"`), never off the entry's presence in\r\n *   the chain — a `middleware`-only layout has no default export and is not a\r\n *   wrapper. Passing bare `sourceFile` strings had every layout read as a\r\n *   rendering one, so boot refused a middleware-only guard chain that the build\r\n *   had already accepted: an application that builds and will not start.\r\n * - MIDDLEWARE and PREFIX are compositions: every layout on the path\r\n *   contributes, outermost first. A guard on an outer layout that the page's own\r\n *   directory knows nothing about is exactly the guard that must still run, and\r\n *   a prefix nobody composed is a URL nobody wrote down.\r\n *\r\n * A chain with more than one RENDERING layout is still refused here, at boot,\r\n * before a single request can observe the wrong document. Like the missing\r\n * app-root refusal below, that arm defends against stale or hand-edited build\r\n * artifacts: the build refuses to emit such a chain, but a manifest can reach a\r\n * running process without that build having produced it.\r\n */\r\ntype LayoutLevel = {\r\n  /**\r\n   * The layout entry the handler's layout slot is registered under, or\r\n   * `undefined` when the page has no layout at all: the layout that RENDERS,\r\n   * or — when none does — the nearest one, which is the slot production has\r\n   * always used and so the choice that changes nothing but the middleware for a\r\n   * chain with no wrapper in it.\r\n   */\r\n  host: PageManifestLayoutEntry | undefined;\r\n  /** Every layout's `prefix`, composed outermost first — `discoverPages`' own reduction. */\r\n  prefix: string;\r\n};\r\n\r\nfunction layoutLevelOf(page: PageManifestPageEntry): LayoutLevel {\r\n  const selection = selectPageLayout(\r\n    page.layouts.map((layout) => ({\r\n      layout: layout.sourceFile,\r\n      renders: typeof (layout.module as LayoutModuleShape).default !== \"undefined\",\r\n    })),\r\n  );\r\n\r\n  if (selection.type === \"rejected\") {\r\n    throw new NestedLayoutsNotSupportedError(page.sourceFile, selection.layouts);\r\n  }\r\n\r\n  return {\r\n    host:\r\n      selection.type === \"selected\"\r\n        ? page.layouts.find((layout) => layout.sourceFile === selection.layout)\r\n        : page.layouts.at(-1),\r\n    prefix: page.layouts.reduce(\r\n      (composed, layout) =>\r\n        composeRoutePath(composed, (layout.module as LayoutModuleShape).prefix ?? \"/\"),\r\n      \"/\",\r\n    ),\r\n  };\r\n}\r\n\r\n/**\r\n * The layout slot's module for one page: the slot host's own namespace, with the\r\n * whole chain's middleware in place of its own — outermost first, which is the\r\n * order stage 3 runs the array in (`execute-page-request.ts:519-524`) and the\r\n * order an outer `optionalAuth` needs in order to have resolved an identity\r\n * before an inner `gate()` checks it.\r\n *\r\n * Deliberately NOT core's route-level `middleware` option: that runs before the\r\n * pipeline's App-level middleware, which would invert outermost-first — the one\r\n * property this composition exists to guarantee.\r\n *\r\n * Built once at registration, not per request: unlike dev, every module here is\r\n * already in memory and cannot change under a running process.\r\n */\r\nfunction composeLayoutLevel(\r\n  page: PageManifestPageEntry,\r\n  host: PageManifestLayoutEntry,\r\n): Record<string, unknown> {\r\n  const hostIndex = page.layouts.indexOf(host);\r\n\r\n  return {\r\n    ...host.module,\r\n    middleware: page.layouts.flatMap((layout) => [\r\n      ...((layout.module as LayoutModuleShape).middleware ?? []),\r\n    ]),\r\n    loader: async (context: Parameters<NonNullable<LayoutModuleShape[\"loader\"]>>[0]) => {\r\n      let hostData: unknown;\r\n\r\n      for (let index = 0; index < page.layouts.length; index++) {\r\n        const value = await (page.layouts[index].module as LayoutModuleShape).loader?.(context);\r\n\r\n        if (value instanceof Response || isLoaderShortCircuit(value)) return value;\n        if (index === hostIndex) hostData = value;\r\n      }\r\n\r\n      return hostData;\r\n    },\r\n  };\r\n}\r\n\r\n/**\r\n * Registers every page the manifest carries into `options.router`.\r\n *\r\n * An empty manifest registers nothing and is not an error: \"built with web, no\r\n * pages\" is a legal state of a built application, and treating it as a failure\r\n * would make an empty project unbootable. A manifest that DOES carry pages but\r\n * no app root is the opposite — every page renders inside the application root,\r\n * so that combination is a broken table rather than an empty one, and it is\r\n * refused before any route exists to serve a request with a missing root.\r\n *\r\n * Two pages composing to the same path is refused the moment the second one is\r\n * seen, naming both — a registration-time failure, rather than a route one of\r\n * them silently loses at runtime.\r\n */\r\nexport function installPageRoutesFromManifest(\r\n  options: InstallPageRoutesFromManifestOptions,\r\n): InstalledManifestPageRoute[] {\r\n  const {\r\n    router,\r\n    manifest,\r\n    hydrationClientModuleUrl,\r\n    clientDir,\r\n    createHandler = createPageRouteHandler,\r\n  } = options;\r\n\r\n  if (manifest.pages.length === 0) return [];\r\n\r\n  const app = manifest.app;\r\n\r\n  if (app === undefined) {\r\n    throw new Error(\r\n      `installPageRoutesFromManifest: this build's page manifest carries ${manifest.pages.length} ` +\r\n        \"page(s) but no application root. Every page renders inside the app component, so no \" +\r\n        \"page can be registered without it. Re-run the build so the generated pages barrel \" +\r\n        \"provides an `app` entry.\",\r\n    );\r\n  }\r\n\r\n  // Ids are the manifest's own `sourceFile` strings and are passed on untouched:\r\n  // the loader below matches them by exact string equality, so resolving,\r\n  // joining or swapping separators on one side of that comparison would turn\r\n  // every lookup into a miss.\r\n  const loadModule = createPageModuleLoader(manifest);\r\n  // The namespace is already statically imported by the generated barrel, but\r\n  // do not hand it to the render pipeline until a request actually fails.\r\n  const loadErrorPage = manifest.errorPage === undefined\r\n    ? undefined\r\n    : async () => manifest.errorPage!.module as ErrorPageModule;\r\n\r\n  // Same partition development makes, on the same rule (the filename), so the\r\n  // two modes cannot disagree about which file is the not-found page. It is\r\n  // taken OUT of the registration loop rather than skipped inside it: every step\r\n  // in there composes and claims a URL, and `404.page.tsx` has none.\r\n  const notFoundPages = manifest.pages.filter((page) => isNotFoundPageFile(page.sourceFile));\r\n  const pages = manifest.pages.filter((page) => !isNotFoundPageFile(page.sourceFile));\r\n\r\n  if (notFoundPages.length > 1) {\r\n    throw new DuplicateNotFoundPageError(notFoundPages.map((page) => page.sourceFile));\r\n  }\r\n\r\n  const notFoundPage = notFoundPages[0];\r\n\r\n  if (notFoundPage !== undefined && (notFoundPage.module as PageModuleShape).route !== undefined) {\r\n    throw new NotFoundPageDeclaresRouteError(notFoundPage.sourceFile);\r\n  }\r\n\r\n  const installed: InstalledManifestPageRoute[] = [];\r\n  const fileByPath = new Map<string, string>();\r\n\r\n  for (const page of pages) {\r\n    const { host: layout, prefix: layoutPrefix } = layoutLevelOf(page);\r\n    const routeExport = (page.module as PageModuleShape).route;\r\n\r\n    const { path: routePath, name } = resolveRoute(routeExport, page.sourceFile);\r\n\r\n    // Explicit wins; otherwise the path is derived from the page's own source\r\n    // location and the layouts on its path — the same rule dev applies at\r\n    // registration (`install-page-routes.ts:377-382`) and discovery applies at\r\n    // build (`discover-pages.ts:925-935`), read here off the manifest's own\r\n    // `sourceFile`s instead of the filesystem.\r\n    const effectivePath =\r\n      routeExport === undefined\r\n        ? deriveFilesystemRoutePath({\r\n            pageFile: webRelativeSourceFile(page.sourceFile),\r\n            layoutPrefixes: layoutPrefixesOf(page),\r\n          })\r\n        : composeRoutePath(layoutPrefix, routePath);\r\n    const existingFile = fileByPath.get(effectivePath);\r\n\r\n    if (existingFile) {\r\n      throw new Error(\r\n        `installPageRoutesFromManifest: composed route path \"${effectivePath}\" (layout ` +\r\n          `prefix \"${layoutPrefix}\" + route.path \"${routePath}\") is declared by two pages — ` +\r\n          `\"${existingFile}\" and \"${page.sourceFile}\". Every page's composed route path must ` +\r\n          \"be unique.\",\r\n      );\r\n    }\r\n\r\n    fileByPath.set(effectivePath, page.sourceFile);\r\n\r\n    // The layout slot's id resolves to the COMPOSED level — every layout's\r\n    // middleware, in chain order — and every other id goes straight to the\r\n    // manifest lookup. A one-layout chain has nothing to compose, so it is left\r\n    // to resolve as the exact namespace object the manifest carries, untouched.\r\n    const composedLayout =\r\n      page.layouts.length > 1 && layout !== undefined\r\n        ? composeLayoutLevel(page, layout)\r\n        : undefined;\r\n\r\n    // Every registered handler gets ITS OWN immutable, ordered, deduped CSS\r\n    // chain: root, then every matched layout outer to inner (`page.layouts`,\r\n    // the manifest's own chain — the same one dev walks as\r\n    // `layoutLevel.chain`), then the page. `PageManifest.clientDir` is present\r\n    // whenever `pages` is non-empty (`page-manifest.ts`), which this loop only\r\n    // ever reaches when it is — `clientDir === undefined` is handled anyway,\r\n    // rather than trusted away, because a caller can still pass this function\r\n    // a manifest that violates its own generator's invariant.\r\n    const stylesheetUrls =\r\n      clientDir === undefined\r\n        ? []\r\n        : productionStylesheetUrls(clientDir, [\r\n            app.sourceFile,\r\n            ...page.layouts.map((pageLayout) => pageLayout.sourceFile),\r\n            page.sourceFile,\r\n          ]);\r\n\r\n    router.get(\r\n      effectivePath,\r\n      createHandler({\r\n        path: effectivePath,\r\n        name,\r\n        appFile: app.sourceFile,\r\n        pageFile: page.sourceFile,\r\n        layoutFile: layout?.sourceFile,\r\n        loadModule:\r\n          composedLayout === undefined\r\n            ? loadModule\r\n            : (moduleId) =>\r\n                moduleId === layout?.sourceFile\r\n                  ? Promise.resolve(composedLayout)\r\n                  : loadModule(moduleId),\r\n        loadRegistrationLayouts: () =>\r\n          Promise.resolve(page.layouts.map((layout) => layout.module)),\r\n        hydrationClientModuleUrl,\r\n        loadErrorPage,\r\n        stylesheetUrls,\r\n      }),\r\n      // `isPage` marks this route as SSR-served. Pages and API routes share one\r\n      // router and one route-name namespace, so the router's duplicate-name\r\n      // error reads this flag to say which claimant is the page.\r\n      { name, isPage: true },\r\n    );\r\n\r\n    installed.push({\r\n      declaredPath: routePath,\r\n      path: effectivePath,\r\n      name,\r\n      file: page.sourceFile,\r\n      layoutFile: layout?.sourceFile,\r\n    });\r\n  }\r\n\r\n  /*\r\n    THE CATCH-ALL — the same route dev registers, built the same way, differing\r\n    only in where a module comes from. Registered last, and registered even when\r\n    the build carried no `404.page.tsx`, so a production deployment answers 404\r\n    with the right STATUS whether or not anyone has designed the page yet.\r\n  */\r\n  router.get(\r\n    NOT_FOUND_ROUTE_PATH,\r\n    createNotFoundRouteHandler({\r\n      renderPage:\r\n        notFoundPage === undefined\r\n          ? undefined\r\n          : createHandler({\r\n              path: NOT_FOUND_ROUTE_PATH,\r\n              name: NOT_FOUND_ROUTE_NAME,\r\n              appFile: app.sourceFile,\r\n              pageFile: notFoundPage.sourceFile,\r\n              // No layout, and therefore no layout middleware — see the dev\r\n              // installer for why the not-found path takes nothing that can\r\n              // redirect or throw.\r\n              layoutFile: undefined,\r\n              loadModule,\r\n              hydrationClientModuleUrl,\r\n              loadErrorPage,\r\n              // NO LAYOUT means no layout CSS either — just root and the\r\n              // not-found page's own stylesheets, same reasoning as above.\r\n              stylesheetUrls:\r\n                clientDir === undefined\r\n                  ? []\r\n                  : productionStylesheetUrls(clientDir, [app.sourceFile, notFoundPage.sourceFile]),\r\n              matchPath: (requestPath) => requestPath,\n              statusForRenderedOk: 404,\n              skipPageLoader: true,\n            }),\n    }),\r\n    // `isPage` for the same reason the dev installer carries it — the router's\r\n    // duplicate-name error reads the flag to say which claimant is the page.\r\n    { name: NOT_FOUND_ROUTE_NAME, isPage: true },\r\n  );\r\n\r\n  /*\r\n    Same publish as the dev installer, for the same reason: `href()` and the\r\n    router must agree, and they only can if both read the one loop that\r\n    registered the routes. Production installs once at boot, so the wholesale\r\n    replacement is a single write before the first request.\r\n  */\r\n  publishRouteTable(installed, \"installPageRoutesFromManifest (production)\");\r\n\r\n  return installed;\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA+HA,SAAS,sBAAsB,YAA4B;CACzD,OAAO,WAAW,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,GAAG;AAChD;AAEA,SAAS,aACP,aACA,YACgC;CAChC,IAAI,gBAAgB,QAAW;EAC7B,MAAM,WAAW,sBAAsB,UAAU;EAEjD,OAAO;GACL,MAAM,0BAA0B,EAAE,SAAS,CAAC;GAC5C,MAAM,0BAA0B,QAAQ;EAC1C;CACF;CAEA,MAAM,YAAY,wBAAwB,WAAW;CAErD,OAAO;EACL,MAAM,UAAU;EAChB,MAAM,UAAU,QAAQ,wBAAwB;GAAE,WAAW,UAAU;GAAM;EAAW,CAAC;CAC3F;AACF;;;;;;;;AASA,SAAS,iBAAiB,MAAqD;CAC7E,OAAO,OAAO,YACZ,KAAK,QAAQ,SAAS,WAAW;EAC/B,MAAM,SAAU,OAAO,OAA6B;EAEpD,IAAI,WAAW,QAAW,OAAO,CAAC;EAElC,MAAM,WAAW,sBAAsB,OAAO,UAAU;EACxD,MAAM,aAAa,SAAS,YAAY,GAAG;EAG3C,OAAO,CAAC,CAFU,eAAe,KAAK,KAAK,SAAS,MAAM,GAAG,UAAU,GAEnD,MAAM,CAAC;CAC7B,CAAC,CACH;AACF;AA2CA,SAAS,cAAc,MAA0C;CAC/D,MAAM,YAAY,iBAChB,KAAK,QAAQ,KAAK,YAAY;EAC5B,QAAQ,OAAO;EACf,SAAS,OAAQ,OAAO,OAA6B,YAAY;CACnE,EAAE,CACJ;CAEA,IAAI,UAAU,SAAS,YACrB,MAAM,IAAI,+BAA+B,KAAK,YAAY,UAAU,OAAO;CAG7E,OAAO;EACL,MACE,UAAU,SAAS,aACf,KAAK,QAAQ,MAAM,WAAW,OAAO,eAAe,UAAU,MAAM,IACpE,KAAK,QAAQ,GAAG,EAAE;EACxB,QAAQ,KAAK,QAAQ,QAClB,UAAU,WACT,iBAAiB,UAAW,OAAO,OAA6B,UAAU,GAAG,GAC/E,GACF;CACF;AACF;;;;;;;;;;;;;;;AAgBA,SAAS,mBACP,MACA,MACyB;CACzB,MAAM,YAAY,KAAK,QAAQ,QAAQ,IAAI;CAE3C,OAAO;EACL,GAAG,KAAK;EACR,YAAY,KAAK,QAAQ,SAAS,WAAW,CAC3C,GAAK,OAAO,OAA6B,cAAc,CAAC,CAC1D,CAAC;EACD,QAAQ,OAAO,YAAqE;GAClF,IAAI;GAEJ,KAAK,IAAI,QAAQ,GAAG,QAAQ,KAAK,QAAQ,QAAQ,SAAS;IACxD,MAAM,QAAQ,MAAO,KAAK,QAAQ,MAAM,CAAC,OAA6B,SAAS,OAAO;IAEtF,IAAI,iBAAiB,YAAY,qBAAqB,KAAK,GAAG,OAAO;IACrE,IAAI,UAAU,WAAW,WAAW;GACtC;GAEA,OAAO;EACT;CACF;AACF;;;;;;;;;;;;;;;AAgBA,SAAgB,8BACd,SAC8B;CAC9B,MAAM,EACJ,QACA,UACA,0BACA,WACA,gBAAgB,2BACd;CAEJ,IAAI,SAAS,MAAM,WAAW,GAAG,OAAO,CAAC;CAEzC,MAAM,MAAM,SAAS;CAErB,IAAI,QAAQ,QACV,MAAM,IAAI,MACR,qEAAqE,SAAS,MAAM,OAAO,kMAI7F;CAOF,MAAM,aAAa,uBAAuB,QAAQ;CAGlD,MAAM,gBAAgB,SAAS,cAAc,SACzC,SACA,YAAY,SAAS,UAAW;CAMpC,MAAM,gBAAgB,SAAS,MAAM,QAAQ,SAAS,mBAAmB,KAAK,UAAU,CAAC;CACzF,MAAM,QAAQ,SAAS,MAAM,QAAQ,SAAS,CAAC,mBAAmB,KAAK,UAAU,CAAC;CAElF,IAAI,cAAc,SAAS,GACzB,MAAM,IAAI,2BAA2B,cAAc,KAAK,SAAS,KAAK,UAAU,CAAC;CAGnF,MAAM,eAAe,cAAc;CAEnC,IAAI,iBAAiB,UAAc,aAAa,OAA2B,UAAU,QACnF,MAAM,IAAI,+BAA+B,aAAa,UAAU;CAGlE,MAAM,YAA0C,CAAC;CACjD,MAAM,6BAAa,IAAI,IAAoB;CAE3C,KAAK,MAAM,QAAQ,OAAO;EACxB,MAAM,EAAE,MAAM,QAAQ,QAAQ,iBAAiB,cAAc,IAAI;EACjE,MAAM,cAAe,KAAK,OAA2B;EAErD,MAAM,EAAE,MAAM,WAAW,SAAS,aAAa,aAAa,KAAK,UAAU;EAO3E,MAAM,gBACJ,gBAAgB,SACZ,0BAA0B;GACxB,UAAU,sBAAsB,KAAK,UAAU;GAC/C,gBAAgB,iBAAiB,IAAI;EACvC,CAAC,IACD,iBAAiB,cAAc,SAAS;EAC9C,MAAM,eAAe,WAAW,IAAI,aAAa;EAEjD,IAAI,cACF,MAAM,IAAI,MACR,uDAAuD,cAAc,oBACxD,aAAa,kBAAkB,UAAU,iCAChD,aAAa,SAAS,KAAK,WAAW,oDAE9C;EAGF,WAAW,IAAI,eAAe,KAAK,UAAU;EAM7C,MAAM,iBACJ,KAAK,QAAQ,SAAS,KAAK,WAAW,SAClC,mBAAmB,MAAM,MAAM,IAC/B;EAUN,MAAM,iBACJ,cAAc,SACV,CAAC,IACD,yBAAyB,WAAW;GAClC,IAAI;GACJ,GAAG,KAAK,QAAQ,KAAK,eAAe,WAAW,UAAU;GACzD,KAAK;EACP,CAAC;EAEP,OAAO,IACL,eACA,cAAc;GACZ,MAAM;GACN;GACA,SAAS,IAAI;GACb,UAAU,KAAK;GACf,YAAY,QAAQ;GACpB,YACE,mBAAmB,SACf,cACC,aACC,aAAa,QAAQ,aACjB,QAAQ,QAAQ,cAAc,IAC9B,WAAW,QAAQ;GAC/B,+BACE,QAAQ,QAAQ,KAAK,QAAQ,KAAK,WAAW,OAAO,MAAM,CAAC;GAC7D;GACA;GACA;EACF,CAAC,GAID;GAAE;GAAM,QAAQ;EAAK,CACvB;EAEA,UAAU,KAAK;GACb,cAAc;GACd,MAAM;GACN;GACA,MAAM,KAAK;GACX,YAAY,QAAQ;EACtB,CAAC;CACH;CAQA,OAAO,SAEL,2BAA2B,EACzB,YACE,iBAAiB,SACb,SACA,cAAc;EACZ;EACA,MAAM;EACN,SAAS,IAAI;EACb,UAAU,aAAa;EAIvB,YAAY;EACZ;EACA;EACA;EAGA,gBACE,cAAc,SACV,CAAC,IACD,yBAAyB,WAAW,CAAC,IAAI,YAAY,aAAa,UAAU,CAAC;EACnF,YAAY,gBAAgB;EAC5B,qBAAqB;EACrB,gBAAgB;CAClB,CAAC,EACT,CAAC,GAGD;EAAE,MAAM;EAAsB,QAAQ;CAAK,CAC7C;CAQA,kBAAkB,WAAW,4CAA4C;CAEzE,OAAO;AACT"}
+{"version":3,"file":"install-page-routes-from-manifest.mjs","names":[],"sources":["../../../../../../../web/src/server/install-page-routes-from-manifest.ts"],"sourcesContent":["/**\r\n * Page-route registration for a built application.\r\n *\r\n * `installPageRoutes` answers \"which pages exist?\" by walking the filesystem\r\n * and \"what is this module?\" by asking Vite to evaluate it. Neither question\r\n * can be asked of a running production process: there is no `app/` tree beside\r\n * the bundle and no Vite. Both answers were therefore moved to build time — the\r\n * generated `pages.ts` barrel statically imported every page, layout and the\r\n * app root and handed them over as a {@link PageManifest}, and this module\r\n * turns that table into registered routes.\r\n *\r\n * WHAT IS DELIBERATELY IDENTICAL TO DEVELOPMENT: the route a page ends up on,\r\n * and the guards that run before it renders. A page's `route` export and the\r\n * `prefix` and `middleware` exports of EVERY layout on its path are read off the\r\n * module namespaces here, at boot, and composed by the same rules dev composes\r\n * them by ({@link layoutLevelOf}, {@link composeLayoutLevel}) — so the URL a page\r\n * answers on and the chain that guards it are decided by the page's own source\r\n * in both modes, and a build cannot quietly disagree with the dev server about\r\n * either.\r\n *\r\n * WHAT IS DELIBERATELY DIFFERENT: this is synchronous. Every module is already\r\n * in memory, so registration has nothing to await; the loader handed to each\r\n * handler is a lookup over the same table, not an evaluation step.\r\n */\r\nimport { composeRoutePath } from \"../routing/compose-route-path\";\r\nimport { deriveFilesystemRoutePath } from \"../routing/filesystem-route\";\r\nimport { NestedLayoutsNotSupportedError, selectPageLayout } from \"../routing/layout-policy\";\r\nimport {\r\n  canonicalizeRouteExport,\r\n  resolvePageRouteCache,\r\n  resolvePageRouteName,\r\n  type PageCacheOptIn,\r\n} from \"../routing/route-identity\";\r\nimport { publishRouteTable } from \"../routing/route-table\";\r\nimport { Response, type Router } from \"@warlock.js/core\";\r\nimport { createPageModuleLoader } from \"./create-page-module-loader\";\r\nimport type { ErrorPageModule } from \"./error-page\";\r\nimport {\r\n  createPageRouteHandler,\r\n  type PageRouteHandler,\r\n  type PageRouteHandlerOptions,\r\n} from \"./create-page-route-handler\";\r\nimport type { PipelineLoader, PipelineMiddleware } from \"./execute-page-request\";\r\nimport { isLoaderShortCircuit } from \"./settle-page-response\";\r\nimport { productionStylesheetUrls } from \"./stylesheet-urls\";\r\nimport {\r\n  createNotFoundRouteHandler,\r\n  DuplicateNotFoundPageError,\r\n  isNotFoundPageFile,\r\n  NotFoundPageDeclaresRouteError,\r\n  NOT_FOUND_ROUTE_NAME,\r\n  NOT_FOUND_ROUTE_PATH,\r\n  type RegisteredRouteShape,\r\n} from \"./not-found-page\";\r\nimport type { PageManifest, PageManifestLayoutEntry, PageManifestPageEntry } from \"./page-manifest\";\r\n\r\n/** A page declares either a bare path or a path plus an explicit route name. */\r\ntype PageRouteExport = string | { path: string; name?: string; cache?: PageCacheOptIn };\r\n\r\n/** The only export this module reads off a page module namespace. */\r\ntype PageModuleShape = {\r\n  route?: PageRouteExport;\r\n};\r\n\r\n/** The exports this module reads off a layout module namespace. */\r\ntype LayoutModuleShape = {\r\n  prefix?: string;\r\n  /**\r\n   * The default export — the thing that puts an element in the document, and\r\n   * therefore the ONLY export that decides whether a layout counts against the\r\n   * single-rendering-layout rule (`../routing/layout-policy.ts`). The manifest\r\n   * carries LOADED modules, so this is a fact rather than a guess, exactly as it\r\n   * is in dev (`install-page-routes.ts:145-150`).\r\n   */\r\n  default?: unknown;\r\n  /** The layout's guards, in the order it declared them. */\r\n  middleware?: readonly PipelineMiddleware[];\r\n  loader?: PipelineLoader;\r\n};\r\n\r\n/**\r\n * How a handler is built for one page. Defaults to `createPageRouteHandler`;\r\n * taking it as an input keeps this module's own job — reading the manifest and\r\n * registering routes — provable without a render pipeline behind it.\r\n */\r\nexport type PageRouteHandlerFactory = (options: PageRouteHandlerOptions) => PageRouteHandler;\r\n\r\nexport type InstalledManifestPageRoute = {\r\n  /** The canonical declared route path, before layout-prefix composition. */\r\n  declaredPath: string;\r\n  /** The composed path the route was registered on. */\r\n  path: string;\r\n  /** The resolved route name; shared namespace with API routes. */\r\n  name: string;\r\n  /** The page's manifest `sourceFile`. */\r\n  file: string;\r\n  /** The layout's manifest `sourceFile`, when the page has one. */\r\n  layoutFile: string | undefined;\r\n};\r\n\r\nexport type InstallPageRoutesFromManifestOptions = {\r\n  router: Router;\r\n  /** The table the generated production barrel provided at import time. */\r\n  manifest: PageManifest;\r\n  /** Browser module loaded after the server-rendered application and payload. */\r\n  hydrationClientModuleUrl?: string;\r\n  /**\r\n   * Where the client build wrote its output — `productionStylesheetUrls`'s own\r\n   * `clientDir` argument, forwarded here rather than pre-read into a flat list:\r\n   * each registered handler needs its OWN chain\r\n   * (`[root, ...outer-to-inner matched layouts, page]`, matched by the\r\n   * manifest's own `sourceFile` ids), not one list shared by every page.\r\n   *\r\n   * OPTIONAL for the same reason `PageManifest.clientDir` is: a build that\r\n   * discovered zero pages emits no client bundle, so there is no directory to\r\n   * read stylesheets from — and no page that could need one either.\r\n   */\r\n  clientDir?: string;\r\n  /** Same helper `dev-server.ts` exports — passed in, never imported. */\r\n  createHandler?: PageRouteHandlerFactory;\r\n};\r\n\r\n/**\r\n * `sourceFile`'s path relative to the web root — `src/web/**`, the only page\r\n * root discovery enumerates (`discoverWebRoots`,\r\n * `web/src/build/discover-pages.ts:210-213`). Manifest `sourceFile`s are\r\n * app-root-relative (`\"src/web/...\"`, `page-manifest.ts`'s own doc comment),\r\n * so dropping the first two segments — `<srcDir>`, then the literal `\"web\"` —\r\n * recovers exactly what `deriveFilesystemRoutePath`/`deriveFilesystemRouteName`\r\n * expect: the same value dev computes as `filesystemPageFileFor`\r\n * (`install-page-routes.ts:101-103`).\r\n */\r\nfunction webRelativeSourceFile(sourceFile: string): string {\r\n  return sourceFile.split(\"/\").slice(2).join(\"/\");\r\n}\r\n\r\n/** Exported for `../routing/route-name-parity.spec.ts`, which proves this and dev's `resolvePageRouteIdentity` agree. */\r\nexport function resolveRoute(\r\n  routeExport: PageRouteExport | undefined,\r\n  sourceFile: string,\r\n): { path: string; name: string } {\r\n  const pageFile = webRelativeSourceFile(sourceFile);\r\n\r\n  if (routeExport === undefined) {\r\n    return {\r\n      path: deriveFilesystemRoutePath({ pageFile }),\r\n      name: resolvePageRouteName(routeExport, pageFile),\r\n    };\r\n  }\r\n\r\n  return {\r\n    path: canonicalizeRouteExport(routeExport, sourceFile).path,\r\n    name: resolvePageRouteName(routeExport, pageFile),\r\n  };\r\n}\r\n\r\n/**\r\n * Every layout's declared `prefix`, keyed by its directory relative to the\r\n * web root — the same table dev builds as `LayoutLevel.prefixesByDirectory`\r\n * (`install-page-routes.ts:214-222`) and the one\r\n * {@link deriveFilesystemRoutePath} uses to let a directory's own layout\r\n * rename the URL segment a bare directory name would otherwise contribute.\r\n */\r\nfunction layoutPrefixesOf(page: PageManifestPageEntry): Record<string, string> {\r\n  return Object.fromEntries(\r\n    page.layouts.flatMap((layout) => {\r\n      const prefix = (layout.module as LayoutModuleShape).prefix;\r\n\r\n      if (prefix === undefined) return [];\r\n\r\n      const relative = webRelativeSourceFile(layout.sourceFile);\r\n      const slashIndex = relative.lastIndexOf(\"/\");\r\n      const directory = slashIndex === -1 ? \"\" : relative.slice(0, slashIndex);\r\n\r\n      return [[directory, prefix]];\r\n    }),\r\n  );\r\n}\r\n\r\n/**\r\n * The page's layout LEVEL, resolved from the whole chain the manifest carries\r\n * rather than from the one layout nearest to it — the same resolution dev makes\r\n * (`install-page-routes.ts:138-164`), against loaded modules instead of Vite's.\r\n *\r\n * The manifest carries the FULL chain, outermost first, and the render pipeline\r\n * has exactly one layout slot per page (`execute-page-request.ts`'s\r\n * `PageRouteEntry[\"triple\"]`), so the chain has to be collapsed into one module\r\n * before it reaches a handler. Two things collapse differently and both matter:\r\n *\r\n * - RENDERING is a selection: at most one layout on the chain may render, and\r\n *   the policy picks it. `renders` is read off the loaded module\r\n *   (`typeof module.default !== \"undefined\"`), never off the entry's presence in\r\n *   the chain — a `middleware`-only layout has no default export and is not a\r\n *   wrapper. Passing bare `sourceFile` strings had every layout read as a\r\n *   rendering one, so boot refused a middleware-only guard chain that the build\r\n *   had already accepted: an application that builds and will not start.\r\n * - MIDDLEWARE and PREFIX are compositions: every layout on the path\r\n *   contributes, outermost first. A guard on an outer layout that the page's own\r\n *   directory knows nothing about is exactly the guard that must still run, and\r\n *   a prefix nobody composed is a URL nobody wrote down.\r\n *\r\n * A chain with more than one RENDERING layout is still refused here, at boot,\r\n * before a single request can observe the wrong document. Like the missing\r\n * app-root refusal below, that arm defends against stale or hand-edited build\r\n * artifacts: the build refuses to emit such a chain, but a manifest can reach a\r\n * running process without that build having produced it.\r\n */\r\ntype LayoutLevel = {\r\n  /**\r\n   * The layout entry the handler's layout slot is registered under, or\r\n   * `undefined` when the page has no layout at all: the layout that RENDERS,\r\n   * or — when none does — the nearest one, which is the slot production has\r\n   * always used and so the choice that changes nothing but the middleware for a\r\n   * chain with no wrapper in it.\r\n   */\r\n  host: PageManifestLayoutEntry | undefined;\r\n  /** Every layout's `prefix`, composed outermost first — `discoverPages`' own reduction. */\r\n  prefix: string;\r\n};\r\n\r\nfunction layoutLevelOf(page: PageManifestPageEntry): LayoutLevel {\r\n  const selection = selectPageLayout(\r\n    page.layouts.map((layout) => ({\r\n      layout: layout.sourceFile,\r\n      renders: typeof (layout.module as LayoutModuleShape).default !== \"undefined\",\r\n    })),\r\n  );\r\n\r\n  if (selection.type === \"rejected\") {\r\n    throw new NestedLayoutsNotSupportedError(page.sourceFile, selection.layouts);\r\n  }\r\n\r\n  return {\r\n    host:\r\n      selection.type === \"selected\"\r\n        ? page.layouts.find((layout) => layout.sourceFile === selection.layout)\r\n        : page.layouts.at(-1),\r\n    prefix: page.layouts.reduce(\r\n      (composed, layout) =>\r\n        composeRoutePath(composed, (layout.module as LayoutModuleShape).prefix ?? \"/\"),\r\n      \"/\",\r\n    ),\r\n  };\r\n}\r\n\r\n/**\r\n * The layout slot's module for one page: the slot host's own namespace, with the\r\n * whole chain's middleware in place of its own — outermost first, which is the\r\n * order stage 3 runs the array in (`execute-page-request.ts:519-524`) and the\r\n * order an outer `optionalAuth` needs in order to have resolved an identity\r\n * before an inner `gate()` checks it.\r\n *\r\n * Deliberately NOT core's route-level `middleware` option: that runs before the\r\n * pipeline's App-level middleware, which would invert outermost-first — the one\r\n * property this composition exists to guarantee.\r\n *\r\n * Built once at registration, not per request: unlike dev, every module here is\r\n * already in memory and cannot change under a running process.\r\n */\r\nfunction composeLayoutLevel(\r\n  page: PageManifestPageEntry,\r\n  host: PageManifestLayoutEntry,\r\n): Record<string, unknown> {\r\n  const hostIndex = page.layouts.indexOf(host);\r\n\r\n  return {\r\n    ...host.module,\r\n    middleware: page.layouts.flatMap((layout) => [\r\n      ...((layout.module as LayoutModuleShape).middleware ?? []),\r\n    ]),\r\n    loader: async (context: Parameters<NonNullable<LayoutModuleShape[\"loader\"]>>[0]) => {\r\n      let hostData: unknown;\r\n\r\n      for (let index = 0; index < page.layouts.length; index++) {\r\n        const value = await (page.layouts[index].module as LayoutModuleShape).loader?.(context);\r\n\r\n        if (value instanceof Response || isLoaderShortCircuit(value)) return value;\r\n        if (index === hostIndex) hostData = value;\r\n      }\r\n\r\n      return hostData;\r\n    },\r\n  };\r\n}\r\n\r\n/**\r\n * Registers every page the manifest carries into `options.router`.\r\n *\r\n * An empty manifest registers nothing and is not an error: \"built with web, no\r\n * pages\" is a legal state of a built application, and treating it as a failure\r\n * would make an empty project unbootable. A manifest that DOES carry pages but\r\n * no app root is the opposite — every page renders inside the application root,\r\n * so that combination is a broken table rather than an empty one, and it is\r\n * refused before any route exists to serve a request with a missing root.\r\n *\r\n * Two pages composing to the same path is refused the moment the second one is\r\n * seen, naming both — a registration-time failure, rather than a route one of\r\n * them silently loses at runtime.\r\n */\r\nexport function installPageRoutesFromManifest(\r\n  options: InstallPageRoutesFromManifestOptions,\r\n): InstalledManifestPageRoute[] {\r\n  const {\r\n    router,\r\n    manifest,\r\n    hydrationClientModuleUrl,\r\n    clientDir,\r\n    createHandler = createPageRouteHandler,\r\n  } = options;\r\n\r\n  if (manifest.pages.length === 0) return [];\r\n\r\n  const app = manifest.app;\r\n\r\n  if (app === undefined) {\r\n    throw new Error(\r\n      `installPageRoutesFromManifest: this build's page manifest carries ${manifest.pages.length} ` +\r\n        \"page(s) but no application root. Every page renders inside the app component, so no \" +\r\n        \"page can be registered without it. Re-run the build so the generated pages barrel \" +\r\n        \"provides an `app` entry.\",\r\n    );\r\n  }\r\n\r\n  // Ids are the manifest's own `sourceFile` strings and are passed on untouched:\r\n  // the loader below matches them by exact string equality, so resolving,\r\n  // joining or swapping separators on one side of that comparison would turn\r\n  // every lookup into a miss.\r\n  const loadModule = createPageModuleLoader(manifest);\r\n  // The namespace is already statically imported by the generated barrel, but\r\n  // do not hand it to the render pipeline until a request actually fails.\r\n  const loadErrorPage =\r\n    manifest.errorPage === undefined\r\n      ? undefined\r\n      : async () => manifest.errorPage!.module as ErrorPageModule;\r\n\r\n  // Same partition development makes, on the same rule (the filename), so the\r\n  // two modes cannot disagree about which file is the not-found page. It is\r\n  // taken OUT of the registration loop rather than skipped inside it: every step\r\n  // in there composes and claims a URL, and `404.page.tsx` has none.\r\n  const notFoundPages = manifest.pages.filter((page) => isNotFoundPageFile(page.sourceFile));\r\n  const pages = manifest.pages.filter((page) => !isNotFoundPageFile(page.sourceFile));\r\n\r\n  if (notFoundPages.length > 1) {\r\n    throw new DuplicateNotFoundPageError(notFoundPages.map((page) => page.sourceFile));\r\n  }\r\n\r\n  const notFoundPage = notFoundPages[0];\r\n\r\n  if (notFoundPage !== undefined && (notFoundPage.module as PageModuleShape).route !== undefined) {\r\n    throw new NotFoundPageDeclaresRouteError(notFoundPage.sourceFile);\r\n  }\r\n\r\n  const installed: InstalledManifestPageRoute[] = [];\r\n  const fileByPath = new Map<string, string>();\r\n\r\n  for (const page of pages) {\r\n    const { host: layout, prefix: layoutPrefix } = layoutLevelOf(page);\r\n    const routeExport = (page.module as PageModuleShape).route;\r\n\r\n    const { path: routePath, name } = resolveRoute(routeExport, page.sourceFile);\r\n\r\n    // Validated at INSTALL time — the same boot-time gate dev applies\r\n    // (`install-page-routes.ts`) — so a malformed `cache` opt-in fails a\r\n    // production boot instead of shipping a page whose freshness window the\r\n    // framework silently guessed.\r\n    const cache = resolvePageRouteCache(routeExport, page.sourceFile);\r\n\r\n    // Explicit wins; otherwise the path is derived from the page's own source\r\n    // location and the layouts on its path — the same rule dev applies at\r\n    // registration (`install-page-routes.ts:377-382`) and discovery applies at\r\n    // build (`discover-pages.ts:925-935`), read here off the manifest's own\r\n    // `sourceFile`s instead of the filesystem.\r\n    const effectivePath =\r\n      routeExport === undefined\r\n        ? deriveFilesystemRoutePath({\r\n            pageFile: webRelativeSourceFile(page.sourceFile),\r\n            layoutPrefixes: layoutPrefixesOf(page),\r\n          })\r\n        : composeRoutePath(layoutPrefix, routePath);\r\n    const existingFile = fileByPath.get(effectivePath);\r\n\r\n    if (existingFile) {\r\n      throw new Error(\r\n        `installPageRoutesFromManifest: composed route path \"${effectivePath}\" (layout ` +\r\n          `prefix \"${layoutPrefix}\" + route.path \"${routePath}\") is declared by two pages — ` +\r\n          `\"${existingFile}\" and \"${page.sourceFile}\". Every page's composed route path must ` +\r\n          \"be unique.\",\r\n      );\r\n    }\r\n\r\n    fileByPath.set(effectivePath, page.sourceFile);\r\n\r\n    // The layout slot's id resolves to the COMPOSED level — every layout's\r\n    // middleware, in chain order — and every other id goes straight to the\r\n    // manifest lookup. A one-layout chain has nothing to compose, so it is left\r\n    // to resolve as the exact namespace object the manifest carries, untouched.\r\n    const composedLayout =\r\n      page.layouts.length > 1 && layout !== undefined\r\n        ? composeLayoutLevel(page, layout)\r\n        : undefined;\r\n\r\n    // Every registered handler gets ITS OWN immutable, ordered, deduped CSS\r\n    // chain: root, then every matched layout outer to inner (`page.layouts`,\r\n    // the manifest's own chain — the same one dev walks as\r\n    // `layoutLevel.chain`), then the page. `PageManifest.clientDir` is present\r\n    // whenever `pages` is non-empty (`page-manifest.ts`), which this loop only\r\n    // ever reaches when it is — `clientDir === undefined` is handled anyway,\r\n    // rather than trusted away, because a caller can still pass this function\r\n    // a manifest that violates its own generator's invariant.\r\n    const stylesheetUrls =\r\n      clientDir === undefined\r\n        ? []\r\n        : productionStylesheetUrls(clientDir, [\r\n            app.sourceFile,\r\n            ...page.layouts.map((pageLayout) => pageLayout.sourceFile),\r\n            page.sourceFile,\r\n          ]);\r\n\r\n    router.get(\r\n      effectivePath,\r\n      createHandler({\r\n        path: effectivePath,\r\n        name,\r\n        appFile: app.sourceFile,\r\n        pageFile: page.sourceFile,\r\n        layoutFile: layout?.sourceFile,\r\n        loadModule:\r\n          composedLayout === undefined\r\n            ? loadModule\r\n            : (moduleId) =>\r\n                moduleId === layout?.sourceFile\r\n                  ? Promise.resolve(composedLayout)\r\n                  : loadModule(moduleId),\r\n        loadRegistrationLayouts: () => Promise.resolve(page.layouts.map((layout) => layout.module)),\r\n        hydrationClientModuleUrl,\r\n        loadErrorPage,\r\n        stylesheetUrls,\r\n        cache,\r\n      }),\r\n      // `isPage` marks this route as SSR-served. Pages and API routes share one\r\n      // router and one route-name namespace, so the router's duplicate-name\r\n      // error reads this flag to say which claimant is the page.\r\n      { name, isPage: true },\r\n    );\r\n\r\n    installed.push({\r\n      declaredPath: routePath,\r\n      path: effectivePath,\r\n      name,\r\n      file: page.sourceFile,\r\n      layoutFile: layout?.sourceFile,\r\n    });\r\n  }\r\n\r\n  /*\r\n    THE CATCH-ALL — the same route dev registers, built the same way, differing\r\n    only in where a module comes from. Registered last, and registered even when\r\n    the build carried no `404.page.tsx`, so a production deployment answers 404\r\n    with the right STATUS whether or not anyone has designed the page yet.\r\n  */\r\n  router.get(\r\n    NOT_FOUND_ROUTE_PATH,\r\n    createNotFoundRouteHandler({\r\n      renderPage:\r\n        notFoundPage === undefined\r\n          ? undefined\r\n          : createHandler({\r\n              path: NOT_FOUND_ROUTE_PATH,\r\n              name: NOT_FOUND_ROUTE_NAME,\r\n              appFile: app.sourceFile,\r\n              pageFile: notFoundPage.sourceFile,\r\n              // No layout, and therefore no layout middleware — see the dev\r\n              // installer for why the not-found path takes nothing that can\r\n              // redirect or throw.\r\n              layoutFile: undefined,\r\n              loadModule,\r\n              hydrationClientModuleUrl,\r\n              loadErrorPage,\r\n              // NO LAYOUT means no layout CSS either — just root and the\r\n              // not-found page's own stylesheets, same reasoning as above.\r\n              stylesheetUrls:\r\n                clientDir === undefined\r\n                  ? []\r\n                  : productionStylesheetUrls(clientDir, [app.sourceFile, notFoundPage.sourceFile]),\r\n              matchPath: (requestPath) => requestPath,\r\n              statusForRenderedOk: 404,\r\n              skipPageLoader: true,\r\n            }),\r\n    }),\r\n    // `isPage` for the same reason the dev installer carries it — the router's\r\n    // duplicate-name error reads the flag to say which claimant is the page.\r\n    { name: NOT_FOUND_ROUTE_NAME, isPage: true },\r\n  );\r\n\r\n  /*\r\n    Same publish as the dev installer, for the same reason: `href()` and the\r\n    router must agree, and they only can if both read the one loop that\r\n    registered the routes. Production installs once at boot, so the wholesale\r\n    replacement is a single write before the first request.\r\n  */\r\n  publishRouteTable(installed, \"installPageRoutesFromManifest (production)\");\r\n\r\n  return installed;\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAoIA,SAAS,sBAAsB,YAA4B;CACzD,OAAO,WAAW,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,GAAG;AAChD;;AAGA,SAAgB,aACd,aACA,YACgC;CAChC,MAAM,WAAW,sBAAsB,UAAU;CAEjD,IAAI,gBAAgB,QAClB,OAAO;EACL,MAAM,0BAA0B,EAAE,SAAS,CAAC;EAC5C,MAAM,qBAAqB,aAAa,QAAQ;CAClD;CAGF,OAAO;EACL,MAAM,wBAAwB,aAAa,UAAU,CAAC,CAAC;EACvD,MAAM,qBAAqB,aAAa,QAAQ;CAClD;AACF;;;;;;;;AASA,SAAS,iBAAiB,MAAqD;CAC7E,OAAO,OAAO,YACZ,KAAK,QAAQ,SAAS,WAAW;EAC/B,MAAM,SAAU,OAAO,OAA6B;EAEpD,IAAI,WAAW,QAAW,OAAO,CAAC;EAElC,MAAM,WAAW,sBAAsB,OAAO,UAAU;EACxD,MAAM,aAAa,SAAS,YAAY,GAAG;EAG3C,OAAO,CAAC,CAFU,eAAe,KAAK,KAAK,SAAS,MAAM,GAAG,UAAU,GAEnD,MAAM,CAAC;CAC7B,CAAC,CACH;AACF;AA2CA,SAAS,cAAc,MAA0C;CAC/D,MAAM,YAAY,iBAChB,KAAK,QAAQ,KAAK,YAAY;EAC5B,QAAQ,OAAO;EACf,SAAS,OAAQ,OAAO,OAA6B,YAAY;CACnE,EAAE,CACJ;CAEA,IAAI,UAAU,SAAS,YACrB,MAAM,IAAI,+BAA+B,KAAK,YAAY,UAAU,OAAO;CAG7E,OAAO;EACL,MACE,UAAU,SAAS,aACf,KAAK,QAAQ,MAAM,WAAW,OAAO,eAAe,UAAU,MAAM,IACpE,KAAK,QAAQ,GAAG,EAAE;EACxB,QAAQ,KAAK,QAAQ,QAClB,UAAU,WACT,iBAAiB,UAAW,OAAO,OAA6B,UAAU,GAAG,GAC/E,GACF;CACF;AACF;;;;;;;;;;;;;;;AAgBA,SAAS,mBACP,MACA,MACyB;CACzB,MAAM,YAAY,KAAK,QAAQ,QAAQ,IAAI;CAE3C,OAAO;EACL,GAAG,KAAK;EACR,YAAY,KAAK,QAAQ,SAAS,WAAW,CAC3C,GAAK,OAAO,OAA6B,cAAc,CAAC,CAC1D,CAAC;EACD,QAAQ,OAAO,YAAqE;GAClF,IAAI;GAEJ,KAAK,IAAI,QAAQ,GAAG,QAAQ,KAAK,QAAQ,QAAQ,SAAS;IACxD,MAAM,QAAQ,MAAO,KAAK,QAAQ,MAAM,CAAC,OAA6B,SAAS,OAAO;IAEtF,IAAI,iBAAiB,YAAY,qBAAqB,KAAK,GAAG,OAAO;IACrE,IAAI,UAAU,WAAW,WAAW;GACtC;GAEA,OAAO;EACT;CACF;AACF;;;;;;;;;;;;;;;AAgBA,SAAgB,8BACd,SAC8B;CAC9B,MAAM,EACJ,QACA,UACA,0BACA,WACA,gBAAgB,2BACd;CAEJ,IAAI,SAAS,MAAM,WAAW,GAAG,OAAO,CAAC;CAEzC,MAAM,MAAM,SAAS;CAErB,IAAI,QAAQ,QACV,MAAM,IAAI,MACR,qEAAqE,SAAS,MAAM,OAAO,kMAI7F;CAOF,MAAM,aAAa,uBAAuB,QAAQ;CAGlD,MAAM,gBACJ,SAAS,cAAc,SACnB,SACA,YAAY,SAAS,UAAW;CAMtC,MAAM,gBAAgB,SAAS,MAAM,QAAQ,SAAS,mBAAmB,KAAK,UAAU,CAAC;CACzF,MAAM,QAAQ,SAAS,MAAM,QAAQ,SAAS,CAAC,mBAAmB,KAAK,UAAU,CAAC;CAElF,IAAI,cAAc,SAAS,GACzB,MAAM,IAAI,2BAA2B,cAAc,KAAK,SAAS,KAAK,UAAU,CAAC;CAGnF,MAAM,eAAe,cAAc;CAEnC,IAAI,iBAAiB,UAAc,aAAa,OAA2B,UAAU,QACnF,MAAM,IAAI,+BAA+B,aAAa,UAAU;CAGlE,MAAM,YAA0C,CAAC;CACjD,MAAM,6BAAa,IAAI,IAAoB;CAE3C,KAAK,MAAM,QAAQ,OAAO;EACxB,MAAM,EAAE,MAAM,QAAQ,QAAQ,iBAAiB,cAAc,IAAI;EACjE,MAAM,cAAe,KAAK,OAA2B;EAErD,MAAM,EAAE,MAAM,WAAW,SAAS,aAAa,aAAa,KAAK,UAAU;EAM3E,MAAM,QAAQ,sBAAsB,aAAa,KAAK,UAAU;EAOhE,MAAM,gBACJ,gBAAgB,SACZ,0BAA0B;GACxB,UAAU,sBAAsB,KAAK,UAAU;GAC/C,gBAAgB,iBAAiB,IAAI;EACvC,CAAC,IACD,iBAAiB,cAAc,SAAS;EAC9C,MAAM,eAAe,WAAW,IAAI,aAAa;EAEjD,IAAI,cACF,MAAM,IAAI,MACR,uDAAuD,cAAc,oBACxD,aAAa,kBAAkB,UAAU,iCAChD,aAAa,SAAS,KAAK,WAAW,oDAE9C;EAGF,WAAW,IAAI,eAAe,KAAK,UAAU;EAM7C,MAAM,iBACJ,KAAK,QAAQ,SAAS,KAAK,WAAW,SAClC,mBAAmB,MAAM,MAAM,IAC/B;EAUN,MAAM,iBACJ,cAAc,SACV,CAAC,IACD,yBAAyB,WAAW;GAClC,IAAI;GACJ,GAAG,KAAK,QAAQ,KAAK,eAAe,WAAW,UAAU;GACzD,KAAK;EACP,CAAC;EAEP,OAAO,IACL,eACA,cAAc;GACZ,MAAM;GACN;GACA,SAAS,IAAI;GACb,UAAU,KAAK;GACf,YAAY,QAAQ;GACpB,YACE,mBAAmB,SACf,cACC,aACC,aAAa,QAAQ,aACjB,QAAQ,QAAQ,cAAc,IAC9B,WAAW,QAAQ;GAC/B,+BAA+B,QAAQ,QAAQ,KAAK,QAAQ,KAAK,WAAW,OAAO,MAAM,CAAC;GAC1F;GACA;GACA;GACA;EACF,CAAC,GAID;GAAE;GAAM,QAAQ;EAAK,CACvB;EAEA,UAAU,KAAK;GACb,cAAc;GACd,MAAM;GACN;GACA,MAAM,KAAK;GACX,YAAY,QAAQ;EACtB,CAAC;CACH;CAQA,OAAO,SAEL,2BAA2B,EACzB,YACE,iBAAiB,SACb,SACA,cAAc;EACZ;EACA,MAAM;EACN,SAAS,IAAI;EACb,UAAU,aAAa;EAIvB,YAAY;EACZ;EACA;EACA;EAGA,gBACE,cAAc,SACV,CAAC,IACD,yBAAyB,WAAW,CAAC,IAAI,YAAY,aAAa,UAAU,CAAC;EACnF,YAAY,gBAAgB;EAC5B,qBAAqB;EACrB,gBAAgB;CAClB,CAAC,EACT,CAAC,GAGD;EAAE,MAAM;EAAsB,QAAQ;CAAK,CAC7C;CAQA,kBAAkB,WAAW,4CAA4C;CAEzE,OAAO;AACT"}

package/esm/server/install-page-routes.d.mts

@@ -1,4 +1,5 @@
 import { composeRoutePath } from "../routing/compose-route-path.mjs";
+import { PageCacheOptIn } from "../routing/route-identity.mjs";
 import { PipelineLoader, PipelineMiddleware } from "./execute-page-request.types.mjs";
 import { Router } from "@warlock.js/core";
 import { ViteDevServer } from "vite";
@@ -7,6 +8,7 @@ import { ViteDevServer } from "vite";
 type PageRouteExport = string | {
   path: string;
   name?: string;
+  cache?: PageCacheOptIn;
 };
 type PageModuleShape = {
   route?: PageRouteExport;
@@ -33,7 +35,7 @@ type LayoutModuleShape = {
 };
 type InstallPageRoutesOptions = {
   router: Router;
-  vite: ViteDevServer; /** v5/app/src — pages live under "<appSrcRoot>/app/*\/web/**" and "<appSrcRoot>/web/**". */
+  vite: ViteDevServer; /** v5/app/src — pages live under "<appSrcRoot>/web/**". */
   appSrcRoot: string; /** v5/app/src/web/root.tsx — the single global app-root file. */
   appFile: string;
   /**

package/esm/server/install-page-routes.mjs

@@ -1,9 +1,9 @@
 import { publishRouteTable } from "../routing/route-table.mjs";
 import { isLoaderShortCircuit } from "./settle-page-response.mjs";
 import { composeRoutePath } from "../routing/compose-route-path.mjs";
-import { deriveFilesystemRouteName, deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
+import { deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
 import { NestedLayoutsNotSupportedError, selectPageLayout } from "../routing/layout-policy.mjs";
-import { canonicalizeRouteExport } from "../routing/route-identity.mjs";
+import { canonicalizeRouteExport, resolvePageRouteCache, resolvePageRouteName } from "../routing/route-identity.mjs";
 import { createPageRouteHandler } from "./create-page-route-handler.mjs";
 import { devHandlerStylesheetUrls } from "./stylesheet-urls.mjs";
 import { DuplicateNotFoundPageError, NOT_FOUND_ROUTE_NAME, NOT_FOUND_ROUTE_PATH, NotFoundPageDeclaresRouteError, createNotFoundRouteHandler, isNotFoundPageFile } from "./not-found-page.mjs";
@@ -39,10 +39,9 @@ import path from "node:path";
 *
 * WHICH PAGES EXIST is answered by {@link discoverPageFiles}
 * (`web/src/build/discover-pages.ts`) — the same walk production's build
-* shares — so this file owns no directory-walking of its own and serves the
-* global root (`<appSrcRoot>/web/**`) exactly as it serves a module's
-* (`<appSrcRoot>/app/<module>/web/**`). WHAT ROUTE A PAGE ANSWERS ON stays
-* this file's own job: each page and its nearest layout are still evaluated
+* shares — so this file owns no directory-walking of its own; it serves the
+* page root (`<appSrcRoot>/web/**`) exactly as discovery enumerates it. WHAT
+* ROUTE A PAGE ANSWERS ON stays this file's own job: each page and its nearest layout are still evaluated
 * through Vite (`vite.ssrLoadModule`), never read statically, because a dev
 * page module must be the one Vite serves, warm cache and all.
 */
@@ -73,12 +72,11 @@ function resolvePageRouteIdentity(routeExport, pageFile, appSrcRoot) {
 	const filesystemPageFile = filesystemPageFileFor(pageFile, appSrcRoot);
 	if (routeExport === void 0) return {
 		declaredPath: deriveFilesystemRoutePath({ pageFile: filesystemPageFile }),
-		name: deriveFilesystemRouteName(filesystemPageFile)
+		name: resolvePageRouteName(routeExport, filesystemPageFile)
 	};
-	const route = canonicalizeRouteExport(routeExport);
 	return {
-		declaredPath: route.path,
-		name: route.name ?? deriveFilesystemRouteName(filesystemPageFile)
+		declaredPath: canonicalizeRouteExport(routeExport, pageFile).path,
+		name: resolvePageRouteName(routeExport, filesystemPageFile)
 	};
 }
 async function resolveLayoutLevel(pageFile, webRoot, loadLayout) {
@@ -157,6 +155,7 @@ async function installPageRoutes(options) {
 		const pageModule = await vite.ssrLoadModule(pageFile);
 		const sourceFile = canonicalSourceFileFor(pageFile, appSrcRoot);
 		const { declaredPath: routePath, name } = resolvePageRouteIdentity(pageModule.route, pageFile, appSrcRoot);
+		const cache = resolvePageRouteCache(pageModule.route, pageFile);
 		const loadLayout = (layoutFile) => vite.ssrLoadModule(layoutFile);
 		const layoutLevel = await resolveLayoutLevel(pageFile, webRoot, loadLayout);
 		const { layoutFile, prefix: layoutPrefix } = layoutLevel;
@@ -185,7 +184,8 @@ async function installPageRoutes(options) {
 			loadRegistrationLayouts: () => Promise.all(layoutLevel.chain.map(loadLayout)),
 			hydrationClientModuleUrl,
 			loadErrorPage,
-			stylesheetUrls
+			stylesheetUrls,
+			cache
 		}), {
 			name,
 			isPage: true

package/esm/server/install-page-routes.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"install-page-routes.mjs","names":[],"sources":["../../../../../../../web/src/server/install-page-routes.ts"],"sourcesContent":["/**\r\n * Registers every page {@link discoverPageFiles} finds under `<appSrcRoot>`\r\n * into Warlock's router (`router.get`, `core/src/router/router.ts:359-361`)\r\n * so `router.scanDevServer(fastify)` —\r\n * the sanctioned dev-server dispatch path (server matching is Warlock's\r\n * router; there is no second server matcher) — picks\r\n * it up. Replaces the two hand-rolled `fastify.get()` calls this file's\r\n * sibling, `dev-server.ts`, used to make directly.\r\n *\r\n * DELIBERATE EXCEPTION to \"web has no core dependency\", same\r\n * reasoning `dev-server.ts`'s own header comment records: this module is not\r\n * exported from either package barrel and is not part of `web/package.json`'s\r\n * dependency graph — dev/CLI bootstrap only.\r\n *\r\n * Scope note: a page's\r\n * `route.path` is now composed with the `prefix` export of EVERY `layout.tsx`\r\n * on its path — outermost first (`composeRoutePath` below) — before\r\n * registration and before the collision check, so `home.page.tsx`\r\n * (`path: \"/\"`, main layout `prefix: \"/\"`) resolves to `/` and\r\n * `products.page.tsx` (`path: \"/\"`, products layout `prefix: \"/products\"`)\r\n * resolves to `/products` — no collision. A page with no `layout.tsx` on its\r\n * path composes against the implicit root prefix `\"/\"` (e.g. `/contact-us`,\r\n * `/hydration-demo`, both unaffected by composition).\r\n *\r\n * WHICH PAGES EXIST is answered by {@link discoverPageFiles}\r\n * (`web/src/build/discover-pages.ts`) — the same walk production's build\r\n * shares — so this file owns no directory-walking of its own and serves the\r\n * global root (`<appSrcRoot>/web/**`) exactly as it serves a module's\r\n * (`<appSrcRoot>/app/<module>/web/**`). WHAT ROUTE A PAGE ANSWERS ON stays\r\n * this file's own job: each page and its nearest layout are still evaluated\r\n * through Vite (`vite.ssrLoadModule`), never read statically, because a dev\r\n * page module must be the one Vite serves, warm cache and all.\r\n */\r\nimport path from \"node:path\";\r\nimport type { ViteDevServer } from \"vite\";\r\nimport {\r\n  discoverPageFiles,\r\n  ErrorPageDeclaresRouteError,\r\n  isErrorPageFile,\r\n  layoutChainFor,\r\n  toPosix,\r\n} from \"../build/discover-pages\";\r\nimport { NonLiteralRouteExportError, readRouteExports } from \"../build/read-route-exports\";\r\nimport { composeRoutePath } from \"../routing/compose-route-path\";\r\nimport {\r\n  deriveFilesystemRouteName,\r\n  deriveFilesystemRoutePath,\r\n} from \"../routing/filesystem-route\";\r\nimport { NestedLayoutsNotSupportedError, selectPageLayout } from \"../routing/layout-policy\";\r\nimport { canonicalizeRouteExport } from \"../routing/route-identity\";\r\nimport { publishRouteTable } from \"../routing/route-table\";\r\nimport { Response, type Router } from \"@warlock.js/core\";\r\nimport { createPageRouteHandler } from \"./create-page-route-handler\";\r\nimport type { ErrorPageModule } from \"./error-page\";\r\nimport type { PipelineLoader, PipelineMiddleware } from \"./execute-page-request\";\nimport { isLoaderShortCircuit } from \"./settle-page-response\";\nimport { devHandlerStylesheetUrls } from \"./stylesheet-urls\";\r\nimport {\r\n  createNotFoundRouteHandler,\r\n  DuplicateNotFoundPageError,\r\n  isNotFoundPageFile,\r\n  NotFoundPageDeclaresRouteError,\r\n  NOT_FOUND_ROUTE_NAME,\r\n  NOT_FOUND_ROUTE_PATH,\r\n  type RegisteredRouteShape,\r\n} from \"./not-found-page\";\r\n\r\n/** Re-exported so `web/src/server/index.ts`'s existing barrel export keeps resolving. */\r\nexport { composeRoutePath };\r\n\r\nexport type PageRouteExport = string | { path: string; name?: string };\r\n\r\nexport type PageModuleShape = {\r\n  route?: PageRouteExport;\r\n};\r\n\r\nexport type InstalledPageRoute = {\r\n  /** The canonical declared route path, before layout-prefix composition. */\r\n  declaredPath: string;\r\n  path: string;\r\n  name: string;\r\n  file: string;\r\n  layoutFile: string | undefined;\r\n};\r\n\r\n/**\r\n * Ownership key for the framework's fallback 404 route. A NUL-prefixed value\r\n * cannot be a real filesystem path, so it cannot collide with an app page's\r\n * canonical source-file key.\r\n */\r\nexport const FRAMEWORK_DEFAULT_NOT_FOUND_SOURCE_FILE = \"\\0warlock:framework-default-404\";\r\n\r\n/**\r\n * The page's application-source-relative POSIX source path used as the router's\r\n * stable ownership key. `appSrcRoot`'s own basename preserves the existing\r\n * `src/web/...` source-file convention.\r\n */\r\nfunction canonicalSourceFileFor(pageFile: string, appSrcRoot: string): string {\r\n  return `${path.basename(appSrcRoot)}/${toPosix(path.relative(appSrcRoot, pageFile))}`;\r\n}\r\n\r\nfunction filesystemPageFileFor(pageFile: string, appSrcRoot: string): string {\r\n  return toPosix(path.relative(path.join(appSrcRoot, \"web\"), pageFile));\r\n}\r\n\r\n/**\r\n * Resolve the stable identity used to distinguish a route-export edit from an\r\n * ordinary component-body edit. The declared path is retained before layout\r\n * composition so `/settings` under `/admin` compares with the next declared\r\n * `/settings`, not with the effective `/admin/settings` route.\r\n */\r\nexport function resolvePageRouteIdentity(\r\n  routeExport: PageRouteExport | undefined,\r\n  pageFile: string,\r\n  appSrcRoot: string,\r\n): Pick<InstalledPageRoute, \"declaredPath\" | \"name\"> {\r\n  const filesystemPageFile = filesystemPageFileFor(pageFile, appSrcRoot);\r\n\r\n  if (routeExport === undefined) {\r\n    return {\r\n      declaredPath: deriveFilesystemRoutePath({ pageFile: filesystemPageFile }),\r\n      name: deriveFilesystemRouteName(filesystemPageFile),\r\n    };\r\n  }\r\n\r\n  const route = canonicalizeRouteExport(routeExport);\r\n\r\n  return {\r\n    declaredPath: route.path,\r\n    name: route.name ?? deriveFilesystemRouteName(filesystemPageFile),\r\n  };\r\n}\r\n\r\nexport type LayoutModuleShape = {\r\n  /** Universal registration hook; invoked on this real namespace, never a composed wrapper. */\r\n  register?: () => unknown;\r\n  prefix?: string;\r\n  /**\r\n   * The default export — the thing that puts an element in the document, and\r\n   * therefore the ONLY export that decides whether a layout counts against the\r\n   * single-rendering-layout rule (`../routing/layout-policy.ts`). In dev the\r\n   * module is loaded, so this is a fact rather than a guess.\r\n   */\r\n  default?: unknown;\r\n  /** The layout's guards, in the order it declared them. */\r\n  middleware?: readonly PipelineMiddleware[];\r\n  loader?: PipelineLoader;\r\n};\r\n\r\n/** How this module gets a layout module namespace — `vite.ssrLoadModule`, in practice. */\r\ntype LoadLayout = (layoutFile: string) => Promise<LayoutModuleShape>;\r\n\r\n/**\r\n * The page's layout LEVEL, resolved from its whole chain rather than from the\r\n * one layout nearest to it.\r\n *\r\n * The render pipeline has exactly one layout slot per page\r\n * (`execute-page-request.ts`'s `PageRouteEntry[\"triple\"]`), so the chain has to\r\n * be collapsed into one module before it reaches a handler. Two things collapse\r\n * differently and both matter:\r\n *\r\n * - RENDERING is a selection: at most one layout on the chain may render, and\r\n *   the policy picks it. `renders` is read off the loaded module\r\n *   (`typeof module.default !== \"undefined\"`), never off the filename — a\r\n *   `middleware`-only layout has no default export and is not a wrapper, and\r\n *   passing a bare path to `selectPageLayout` would have it read as a rendering\r\n *   one, which is the conservative default and the wrong answer here.\r\n * - MIDDLEWARE and PREFIX are compositions: every layout on the path\r\n *   contributes, outermost first. A guard on an outer layout that the page's\r\n *   own directory knows nothing about is exactly the guard that must still run,\r\n *   and a prefix nobody composed is a URL nobody wrote down.\r\n */\r\ntype LayoutLevel = {\r\n  /** Every `layout.tsx` from the web root down to the page's directory, outermost first. */\r\n  chain: string[];\r\n  /**\r\n   * The module id the handler's layout slot is registered under, or `undefined`\r\n   * when the page has no layout at all: the layout that RENDERS, or — when none\r\n   * does — the nearest one, which is the slot dev has always used and so the\r\n   * choice that changes nothing but the middleware for a chain with no wrapper\r\n   * in it.\r\n   */\r\n  layoutFile: string | undefined;\r\n  /** Every layout's `prefix`, composed outermost first — `discoverPages`' own reduction. */\r\n  prefix: string;\r\n  /** Declared prefixes keyed by layout directory relative to this page's web root. */\r\n  prefixesByDirectory: Readonly<Record<string, string>>;\r\n};\r\n\r\nasync function resolveLayoutLevel(\r\n  pageFile: string,\r\n  webRoot: string,\r\n  loadLayout: LoadLayout,\r\n): Promise<LayoutLevel> {\r\n  const chain = layoutChainFor(pageFile, webRoot);\r\n  const modules = await Promise.all(chain.map(loadLayout));\r\n  const selection = selectPageLayout(\r\n    chain.map((layout, index) => ({\r\n      layout,\r\n      renders: typeof modules[index].default !== \"undefined\",\r\n    })),\r\n  );\r\n\r\n  if (selection.type === \"rejected\") {\r\n    throw new NestedLayoutsNotSupportedError(pageFile, selection.layouts);\r\n  }\r\n\r\n  return {\r\n    chain,\r\n    layoutFile: selection.type === \"selected\" ? selection.layout : chain.at(-1),\r\n    prefix: modules.reduce(\r\n      (composed, layoutModule) => composeRoutePath(composed, layoutModule.prefix ?? \"/\"),\r\n      \"/\",\r\n    ),\r\n    prefixesByDirectory: Object.fromEntries(\r\n      chain.flatMap((layoutFile, index) => {\r\n        const prefix = modules[index].prefix;\r\n\r\n        return prefix === undefined\r\n          ? []\r\n          : [[toPosix(path.relative(webRoot, path.dirname(layoutFile))), prefix]];\r\n      }),\r\n    ),\r\n  };\r\n}\r\n\r\n/**\r\n * The layout slot's module for ONE request: the slot host's own namespace, with\r\n * the whole chain's middleware in place of its own — outermost first, which is\r\n * the order stage 3 runs the array in (`execute-page-request.ts:519-524`) and\r\n * the order an outer `optionalAuth` needs in order to have resolved an identity\r\n * before an inner `gate()` checks it.\r\n *\r\n * Loaded per call, not once at install time: a dev layout module must be the\r\n * one Vite is currently serving, edits and all.\r\n */\r\nasync function composeLayoutLevel(\r\n  level: LayoutLevel & { layoutFile: string },\r\n  loadLayout: LoadLayout,\r\n): Promise<LayoutModuleShape> {\r\n  const modules = await Promise.all(level.chain.map(loadLayout));\r\n  const hostIndex = level.chain.indexOf(level.layoutFile);\r\n  const host = modules[hostIndex];\r\n\r\n  return {\r\n    ...host,\r\n    middleware: modules.flatMap(layoutModule => [...(layoutModule.middleware ?? [])]),\r\n    loader: async (context) => {\r\n      let hostData: unknown;\r\n\r\n      for (let index = 0; index < modules.length; index++) {\r\n        const value = await modules[index].loader?.(context);\r\n\r\n        if (value instanceof Response || isLoaderShortCircuit(value)) return value;\n        if (index === hostIndex) hostData = value;\r\n      }\r\n\r\n      return hostData;\r\n    },\r\n  };\r\n}\r\n\r\nexport type InstallPageRoutesOptions = {\r\n  router: Router;\r\n  vite: ViteDevServer;\r\n  /** v5/app/src — pages live under \"<appSrcRoot>/app/*\\/web/**\" and \"<appSrcRoot>/web/**\". */\r\n  appSrcRoot: string;\r\n  /** v5/app/src/web/root.tsx — the single global app-root file. */\r\n  appFile: string;\r\n  /**\r\n   * The application root Vite's dev server serves from — `dev-server.ts`'s\r\n   * `paths.appRoot`, i.e. `<appRoot>/src === appSrcRoot` by default. Every\r\n   * handler's stylesheet URLs are expressed relative to THIS, because that is\r\n   * the root Vite's dev server actually resolves `/…` URLs against\r\n   * (`stylesheet-urls.ts`'s `devStylesheetUrls`) — not `appSrcRoot`, which is\r\n   * one directory level in.\r\n   *\r\n   * OPTIONAL and defaulted to `path.dirname(appSrcRoot)`: the caller that\r\n   * wires dev boot (`web-connector.ts`) does not pass this field today, and\r\n   * that default is exactly the relationship it constructs `appSrcRoot` from\r\n   * (`appSrcRoot = path.join(appRoot, \"src\")`) — correct for every actual\r\n   * deployment, and overridable by a caller with a non-default layout.\r\n   */\r\n  appRoot?: string;\r\n  /** Browser module loaded after the server-rendered application and payload. */\r\n  hydrationClientModuleUrl?: string;\r\n  /**\r\n   * UNUSED. Retained on this type only because `web-connector.ts` still builds\r\n   * an options object naming it (`devStylesheetUrls(paths.appRoot,\r\n   * paths.appFile)`, computed once for the whole application). Each handler\r\n   * now computes its OWN stylesheet chain — `[root, ...outer-to-inner matched\r\n   * layouts, page]`, via `devHandlerStylesheetUrls` — inside the registration\r\n   * loop below, because a single application-wide list cannot express \"this\r\n   * page's own CSS\" without also carrying every other page's.\r\n   */\r\n  stylesheetUrls?: readonly string[];\r\n  /** Same helper `dev-server.ts` exports — passed in, not imported, to avoid a dev-server.ts <-> this-file cycle. */\r\n};\r\n\r\n/**\r\n * Registers every discoverable page into `options.router`. Throws\r\n * IMMEDIATELY, naming both files, the moment two pages declare the same\r\n * `route.path` — a registration-time failure, not a runtime 404 one of them\r\n * silently loses.\r\n *\r\n * Pages with no `route` export derive their path and name from their location\r\n * below `src/web`, using the same pure filesystem-routing helper as the build.\r\n */\r\nexport async function installPageRoutes(\r\n  options: InstallPageRoutesOptions,\r\n): Promise<InstalledPageRoute[]> {\r\n  const {\r\n    router,\r\n    vite,\r\n    appSrcRoot,\r\n    appFile,\r\n    hydrationClientModuleUrl,\r\n  } = options;\r\n  // See `InstallPageRoutesOptions.appRoot` for why this default, not\r\n  // `appSrcRoot` itself, is the root every handler's CSS is resolved against.\r\n  const stylesheetRoot = options.appRoot ?? path.dirname(appSrcRoot);\r\n  const discovered = [...discoverPageFiles(appSrcRoot)].sort((left, right) =>\r\n    left.pageFile < right.pageFile ? -1 : left.pageFile > right.pageFile ? 1 : 0,\r\n  );\r\n\r\n  // THE NOT-FOUND PAGE IS TAKEN OUT OF THE ORDINARY LOOP, not filtered inside\r\n  // it. It has no `route` export to read, no path to compose and no collision\r\n  // to check — every step below is about a page with a URL, and `404.page.tsx`\r\n  // does not have one. Registering it here would put it at `/404`, which is not\r\n  // a page anybody asked to be able to visit.\r\n  const errorPageFiles = discovered.filter((page) => isErrorPageFile(page.pageFile));\r\n  const notFoundPageFiles = discovered.filter((page) => isNotFoundPageFile(page.pageFile));\r\n  const pageFiles = discovered.filter(\r\n    (page) => !isNotFoundPageFile(page.pageFile) && !isErrorPageFile(page.pageFile),\r\n  );\r\n\r\n  if (errorPageFiles.length > 1) {\r\n    throw new Error(`Two error pages were found: ${errorPageFiles.map((page) => page.pageFile).join(\", \")}.`);\r\n  }\r\n\r\n  const errorPageFile = errorPageFiles[0]?.pageFile;\r\n\r\n  // Parse only: the error boundary must remain lazy until a request actually\r\n  // fails, while a route export is still rejected at install time.\r\n  if (errorPageFile !== undefined) {\r\n    const declarations = readRouteExports(errorPageFile);\r\n    if (!declarations.ok) throw new NonLiteralRouteExportError(declarations.rejection);\r\n    if (declarations.route !== undefined) throw new ErrorPageDeclaresRouteError(errorPageFile);\r\n  }\r\n  const loadErrorPage = errorPageFile === undefined\r\n    ? undefined\r\n    : () => vite.ssrLoadModule(errorPageFile) as Promise<ErrorPageModule>;\r\n\r\n  if (notFoundPageFiles.length > 1) {\r\n    throw new DuplicateNotFoundPageError(notFoundPageFiles.map((page) => page.pageFile));\r\n  }\r\n\r\n  const installed: InstalledPageRoute[] = [];\r\n  const fileByPath = new Map<string, string>();\r\n\r\n  for (const { pageFile, webRoot } of pageFiles) {\r\n    const pageModule = (await vite.ssrLoadModule(pageFile)) as PageModuleShape;\r\n\r\n    const sourceFile = canonicalSourceFileFor(pageFile, appSrcRoot);\r\n\r\n    // Route identity is explicit when declared and filesystem-derived otherwise.\r\n    const { declaredPath: routePath, name } = resolvePageRouteIdentity(\r\n      pageModule.route,\r\n      pageFile,\r\n      appSrcRoot,\r\n    );\r\n\r\n    const loadLayout: LoadLayout = layoutFile =>\r\n      vite.ssrLoadModule(layoutFile) as Promise<LayoutModuleShape>;\r\n    const layoutLevel = await resolveLayoutLevel(pageFile, webRoot, loadLayout);\r\n    const { layoutFile, prefix: layoutPrefix } = layoutLevel;\r\n\r\n    const effectivePath = pageModule.route === undefined\r\n      ? deriveFilesystemRoutePath({\r\n          pageFile: filesystemPageFileFor(pageFile, appSrcRoot),\r\n          layoutPrefixes: layoutLevel.prefixesByDirectory,\r\n        })\r\n      : composeRoutePath(layoutPrefix, routePath);\r\n\r\n    const existingFile = fileByPath.get(effectivePath);\r\n\r\n    if (existingFile) {\r\n      throw new Error(\r\n        `installPageRoutes: composed route path \"${effectivePath}\" (layout ` +\r\n          `prefix \"${layoutPrefix}\" + route.path \"${routePath}\") is declared by two ` +\r\n          `pages (web/src/server/install-page-routes.ts) — \"${existingFile}\" and ` +\r\n          `\"${pageFile}\". Every page's composed route path must be unique.`,\r\n      );\r\n    }\r\n\r\n    fileByPath.set(effectivePath, pageFile);\r\n\r\n    // Every registered handler gets ITS OWN immutable, ordered, deduped CSS\r\n    // chain: root, then every matched layout outer to inner\r\n    // (`layoutLevel.chain`), then the page — the same order the render\r\n    // pipeline loads that chain in, so cascade order matches load order.\r\n    // Computed once here, at registration, not per request: dev re-registers\r\n    // on every restart, so a stale chain cannot outlive the source edit that\r\n    // changed it.\r\n    const stylesheetUrls = devHandlerStylesheetUrls(stylesheetRoot, [\r\n      appFile,\r\n      ...layoutLevel.chain,\r\n      pageFile,\r\n    ]);\r\n\r\n    await router.withSourceFile(sourceFile, () =>\r\n      router.get(\r\n        effectivePath,\r\n        // The handler itself is `createPageRouteHandler`\r\n        // (`web/src/server/create-page-route-handler.ts`) — a named seam a\r\n        // future `type: \"page\"` route can bind to, and testable without a Vite\r\n        // server. Vite appears here only as the dev answer to \"how do I load a\r\n        // module\"; the handler takes that as an input and knows nothing else\r\n        // about it.\r\n        createPageRouteHandler({\r\n          path: effectivePath,\r\n          name,\r\n          appFile,\r\n          pageFile,\r\n          layoutFile,\r\n          // The layout slot's id resolves to the COMPOSED level — every layout's\r\n          // middleware, in chain order — and every other id goes straight to\r\n          // Vite. A one-layout chain has nothing to compose, so it is left to\r\n          // resolve as the exact module Vite hands back, untouched.\r\n          loadModule:\r\n            layoutLevel.chain.length > 1 && layoutFile !== undefined\r\n              ? moduleId =>\r\n                  moduleId === layoutFile\r\n                    ? composeLayoutLevel({ ...layoutLevel, layoutFile }, loadLayout)\r\n                    : vite.ssrLoadModule(moduleId)\r\n              : moduleId => vite.ssrLoadModule(moduleId),\r\n          // Registration tracks real module namespaces, not the composed\r\n          // layout wrapper above. Loading the raw chain per request also lets\r\n          // Vite hand over a replacement namespace after an HMR update; the\r\n          // helper's WeakSet then gives that new identity its one invocation.\r\n          loadRegistrationLayouts: () => Promise.all(layoutLevel.chain.map(loadLayout)),\r\n          hydrationClientModuleUrl,\r\n          loadErrorPage,\r\n          stylesheetUrls,\r\n        }),\r\n        // `isPage` marks this route as SSR-served. Pages and API routes share one\r\n        // router and one route-name namespace, so the router's duplicate-name\r\n        // error reads this flag to say which claimant is the page.\r\n        { name, isPage: true },\r\n      ),\r\n    );\r\n\r\n    installed.push({\r\n      declaredPath: routePath,\r\n      path: effectivePath,\r\n      name,\r\n      file: pageFile,\r\n      layoutFile,\r\n    });\r\n  }\r\n\r\n  /*\r\n    THE CATCH-ALL, registered LAST and only when this application has a page\r\n    surface at all. \"Configured with web, no pages yet\" is a legal state, and an\r\n    application serving no pages has no page 404 to answer with — its unmatched\r\n    URLs stay core's to answer, exactly as they are today.\r\n\r\n    Registered even when the application ships no `404.page.tsx`: the framework\r\n    default still answers 404, so an application that has not written one yet\r\n    gets the right STATUS from the first request, and adding the file later\r\n    changes the body and nothing else.\r\n  */\r\n  if (pageFiles.length > 0 || notFoundPageFiles.length > 0) {\r\n    const notFoundPageFile = notFoundPageFiles[0]?.pageFile;\r\n\r\n    // Read at INSTALL time, so a `route` export on the not-found page is\r\n    // refused at boot with everything else — not on the first request that\r\n    // misses, which is the one request nobody is watching.\r\n    if (notFoundPageFile !== undefined) {\r\n      const notFoundModule = (await vite.ssrLoadModule(notFoundPageFile)) as PageModuleShape;\r\n\r\n      if (notFoundModule.route !== undefined) {\r\n        throw new NotFoundPageDeclaresRouteError(notFoundPageFile);\r\n      }\r\n    }\r\n\r\n    const registerNotFoundRoute = () =>\r\n      router.get(\r\n        NOT_FOUND_ROUTE_PATH,\r\n        createNotFoundRouteHandler({\r\n          renderPage:\r\n            notFoundPageFile === undefined\r\n              ? undefined\r\n              : createPageRouteHandler({\r\n                  path: NOT_FOUND_ROUTE_PATH,\r\n                  name: NOT_FOUND_ROUTE_NAME,\r\n                  appFile,\r\n                  pageFile: notFoundPageFile,\r\n                  // NO LAYOUT, deliberately, and it is the same trade as \"no\r\n                  // loader on the 404 page\": a layout brings its whole chain's\r\n                  // middleware with it, and a guard that redirects or throws on\r\n                  // the not-found path turns a missing page into an incident. The\r\n                  // page renders inside the application root and nothing else.\r\n                  layoutFile: undefined,\r\n                  loadModule: (moduleId) => vite.ssrLoadModule(moduleId),\r\n                  hydrationClientModuleUrl,\r\n                  loadErrorPage,\r\n                  // NO LAYOUT means no layout CSS either — just root and the\r\n                  // not-found page's own stylesheets, same reasoning as above.\r\n                  stylesheetUrls: devHandlerStylesheetUrls(stylesheetRoot, [\r\n                    appFile,\r\n                    notFoundPageFile,\r\n                  ]),\r\n                  // The URL that missed IS this route's pattern for this request.\r\n                  matchPath: (requestPath) => requestPath,\n                  statusForRenderedOk: 404,\n                  skipPageLoader: true,\n                }),\n        }),\r\n        // `isPage` for the same reason every other page route carries it: the\r\n        // router's duplicate-name error reads the flag to say which claimant is\r\n        // the page.\r\n        { name: NOT_FOUND_ROUTE_NAME, isPage: true },\r\n      );\r\n\r\n    if (notFoundPageFile === undefined) {\r\n      await router.withSourceFile(FRAMEWORK_DEFAULT_NOT_FOUND_SOURCE_FILE, registerNotFoundRoute);\r\n    } else {\r\n      await router.withSourceFile(\r\n        canonicalSourceFileFor(notFoundPageFile, appSrcRoot),\r\n        registerNotFoundRoute,\r\n      );\r\n    }\r\n  }\r\n\r\n  /*\r\n    Published from the SAME loop that registered the routes, so `href()` and the\r\n    router cannot disagree about where a name points. It happens here rather\r\n    than in the caller because a caller that forgets leaves every `<Link>` on\r\n    the server throwing at render — and dev republishes on every restart, which\r\n    is why the table replaces wholesale instead of merging: a deleted page's\r\n    name has to stop resolving.\r\n  */\r\n  publishRouteTable(installed, \"installPageRoutes (dev)\");\r\n\r\n  return installed;\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA0FA,MAAa,0CAA0C;;;;;;AAOvD,SAAS,uBAAuB,UAAkB,YAA4B;CAC5E,OAAO,GAAG,KAAK,SAAS,UAAU,EAAE,GAAG,QAAQ,KAAK,SAAS,YAAY,QAAQ,CAAC;AACpF;AAEA,SAAS,sBAAsB,UAAkB,YAA4B;CAC3E,OAAO,QAAQ,KAAK,SAAS,KAAK,KAAK,YAAY,KAAK,GAAG,QAAQ,CAAC;AACtE;;;;;;;AAQA,SAAgB,yBACd,aACA,UACA,YACmD;CACnD,MAAM,qBAAqB,sBAAsB,UAAU,UAAU;CAErE,IAAI,gBAAgB,QAClB,OAAO;EACL,cAAc,0BAA0B,EAAE,UAAU,mBAAmB,CAAC;EACxE,MAAM,0BAA0B,kBAAkB;CACpD;CAGF,MAAM,QAAQ,wBAAwB,WAAW;CAEjD,OAAO;EACL,cAAc,MAAM;EACpB,MAAM,MAAM,QAAQ,0BAA0B,kBAAkB;CAClE;AACF;AA0DA,eAAe,mBACb,UACA,SACA,YACsB;CACtB,MAAM,QAAQ,eAAe,UAAU,OAAO;CAC9C,MAAM,UAAU,MAAM,QAAQ,IAAI,MAAM,IAAI,UAAU,CAAC;CACvD,MAAM,YAAY,iBAChB,MAAM,KAAK,QAAQ,WAAW;EAC5B;EACA,SAAS,OAAO,QAAQ,MAAM,CAAC,YAAY;CAC7C,EAAE,CACJ;CAEA,IAAI,UAAU,SAAS,YACrB,MAAM,IAAI,+BAA+B,UAAU,UAAU,OAAO;CAGtE,OAAO;EACL;EACA,YAAY,UAAU,SAAS,aAAa,UAAU,SAAS,MAAM,GAAG,EAAE;EAC1E,QAAQ,QAAQ,QACb,UAAU,iBAAiB,iBAAiB,UAAU,aAAa,UAAU,GAAG,GACjF,GACF;EACA,qBAAqB,OAAO,YAC1B,MAAM,SAAS,YAAY,UAAU;GACnC,MAAM,SAAS,QAAQ,MAAM,CAAC;GAE9B,OAAO,WAAW,SACd,CAAC,IACD,CAAC,CAAC,QAAQ,KAAK,SAAS,SAAS,KAAK,QAAQ,UAAU,CAAC,CAAC,GAAG,MAAM,CAAC;EAC1E,CAAC,CACH;CACF;AACF;;;;;;;;;;;AAYA,eAAe,mBACb,OACA,YAC4B;CAC5B,MAAM,UAAU,MAAM,QAAQ,IAAI,MAAM,MAAM,IAAI,UAAU,CAAC;CAC7D,MAAM,YAAY,MAAM,MAAM,QAAQ,MAAM,UAAU;CAGtD,OAAO;EACL,GAHW,QAAQ;EAInB,YAAY,QAAQ,SAAQ,iBAAgB,CAAC,GAAI,aAAa,cAAc,CAAC,CAAE,CAAC;EAChF,QAAQ,OAAO,YAAY;GACzB,IAAI;GAEJ,KAAK,IAAI,QAAQ,GAAG,QAAQ,QAAQ,QAAQ,SAAS;IACnD,MAAM,QAAQ,MAAM,QAAQ,MAAM,CAAC,SAAS,OAAO;IAEnD,IAAI,iBAAiB,YAAY,qBAAqB,KAAK,GAAG,OAAO;IACrE,IAAI,UAAU,WAAW,WAAW;GACtC;GAEA,OAAO;EACT;CACF;AACF;;;;;;;;;;AAgDA,eAAsB,kBACpB,SAC+B;CAC/B,MAAM,EACJ,QACA,MACA,YACA,SACA,6BACE;CAGJ,MAAM,iBAAiB,QAAQ,WAAW,KAAK,QAAQ,UAAU;CACjE,MAAM,aAAa,CAAC,GAAG,kBAAkB,UAAU,CAAC,CAAC,CAAC,MAAM,MAAM,UAChE,KAAK,WAAW,MAAM,WAAW,KAAK,KAAK,WAAW,MAAM,WAAW,IAAI,CAC7E;CAOA,MAAM,iBAAiB,WAAW,QAAQ,SAAS,gBAAgB,KAAK,QAAQ,CAAC;CACjF,MAAM,oBAAoB,WAAW,QAAQ,SAAS,mBAAmB,KAAK,QAAQ,CAAC;CACvF,MAAM,YAAY,WAAW,QAC1B,SAAS,CAAC,mBAAmB,KAAK,QAAQ,KAAK,CAAC,gBAAgB,KAAK,QAAQ,CAChF;CAEA,IAAI,eAAe,SAAS,GAC1B,MAAM,IAAI,MAAM,+BAA+B,eAAe,KAAK,SAAS,KAAK,QAAQ,CAAC,CAAC,KAAK,IAAI,EAAE,EAAE;CAG1G,MAAM,gBAAgB,eAAe,EAAE,EAAE;CAIzC,IAAI,kBAAkB,QAAW;EAC/B,MAAM,eAAe,iBAAiB,aAAa;EACnD,IAAI,CAAC,aAAa,IAAI,MAAM,IAAI,2BAA2B,aAAa,SAAS;EACjF,IAAI,aAAa,UAAU,QAAW,MAAM,IAAI,4BAA4B,aAAa;CAC3F;CACA,MAAM,gBAAgB,kBAAkB,SACpC,eACM,KAAK,cAAc,aAAa;CAE1C,IAAI,kBAAkB,SAAS,GAC7B,MAAM,IAAI,2BAA2B,kBAAkB,KAAK,SAAS,KAAK,QAAQ,CAAC;CAGrF,MAAM,YAAkC,CAAC;CACzC,MAAM,6BAAa,IAAI,IAAoB;CAE3C,KAAK,MAAM,EAAE,UAAU,aAAa,WAAW;EAC7C,MAAM,aAAc,MAAM,KAAK,cAAc,QAAQ;EAErD,MAAM,aAAa,uBAAuB,UAAU,UAAU;EAG9D,MAAM,EAAE,cAAc,WAAW,SAAS,yBACxC,WAAW,OACX,UACA,UACF;EAEA,MAAM,cAAyB,eAC7B,KAAK,cAAc,UAAU;EAC/B,MAAM,cAAc,MAAM,mBAAmB,UAAU,SAAS,UAAU;EAC1E,MAAM,EAAE,YAAY,QAAQ,iBAAiB;EAE7C,MAAM,gBAAgB,WAAW,UAAU,SACvC,0BAA0B;GACxB,UAAU,sBAAsB,UAAU,UAAU;GACpD,gBAAgB,YAAY;EAC9B,CAAC,IACD,iBAAiB,cAAc,SAAS;EAE5C,MAAM,eAAe,WAAW,IAAI,aAAa;EAEjD,IAAI,cACF,MAAM,IAAI,MACR,2CAA2C,cAAc,oBAC5C,aAAa,kBAAkB,UAAU,yEACA,aAAa,SAC7D,SAAS,oDACjB;EAGF,WAAW,IAAI,eAAe,QAAQ;EAStC,MAAM,iBAAiB,yBAAyB,gBAAgB;GAC9D;GACA,GAAG,YAAY;GACf;EACF,CAAC;EAED,MAAM,OAAO,eAAe,kBAC1B,OAAO,IACL,eAOA,uBAAuB;GACrB,MAAM;GACN;GACA;GACA;GACA;GAKA,YACE,YAAY,MAAM,SAAS,KAAK,eAAe,UAC3C,aACE,aAAa,aACT,mBAAmB;IAAE,GAAG;IAAa;GAAW,GAAG,UAAU,IAC7D,KAAK,cAAc,QAAQ,KACjC,aAAY,KAAK,cAAc,QAAQ;GAK7C,+BAA+B,QAAQ,IAAI,YAAY,MAAM,IAAI,UAAU,CAAC;GAC5E;GACA;GACA;EACF,CAAC,GAID;GAAE;GAAM,QAAQ;EAAK,CACvB,CACF;EAEA,UAAU,KAAK;GACb,cAAc;GACd,MAAM;GACN;GACA,MAAM;GACN;EACF,CAAC;CACH;CAaA,IAAI,UAAU,SAAS,KAAK,kBAAkB,SAAS,GAAG;EACxD,MAAM,mBAAmB,kBAAkB,EAAE,EAAE;EAK/C,IAAI,qBAAqB,QAGvB;QAAI,MAF0B,KAAK,cAAc,gBAAgB,EAE/C,CAAC,UAAU,QAC3B,MAAM,IAAI,+BAA+B,gBAAgB;EAC3D;EAGF,MAAM,8BACJ,OAAO,SAEL,2BAA2B,EACzB,YACE,qBAAqB,SACjB,SACA,uBAAuB;GACrB;GACA,MAAM;GACN;GACA,UAAU;GAMV,YAAY;GACZ,aAAa,aAAa,KAAK,cAAc,QAAQ;GACrD;GACA;GAGA,gBAAgB,yBAAyB,gBAAgB,CACvD,SACA,gBACF,CAAC;GAED,YAAY,gBAAgB;GAC5B,qBAAqB;GACrB,gBAAgB;EAClB,CAAC,EACT,CAAC,GAID;GAAE,MAAM;GAAsB,QAAQ;EAAK,CAC7C;EAEF,IAAI,qBAAqB,QACvB,MAAM,OAAO,eAAe,yCAAyC,qBAAqB;OAE1F,MAAM,OAAO,eACX,uBAAuB,kBAAkB,UAAU,GACnD,qBACF;CAEJ;CAUA,kBAAkB,WAAW,yBAAyB;CAEtD,OAAO;AACT"}
+{"version":3,"file":"install-page-routes.mjs","names":[],"sources":["../../../../../../../web/src/server/install-page-routes.ts"],"sourcesContent":["/**\r\n * Registers every page {@link discoverPageFiles} finds under `<appSrcRoot>`\r\n * into Warlock's router (`router.get`, `core/src/router/router.ts:359-361`)\r\n * so `router.scanDevServer(fastify)` —\r\n * the sanctioned dev-server dispatch path (server matching is Warlock's\r\n * router; there is no second server matcher) — picks\r\n * it up. Replaces the two hand-rolled `fastify.get()` calls this file's\r\n * sibling, `dev-server.ts`, used to make directly.\r\n *\r\n * DELIBERATE EXCEPTION to \"web has no core dependency\", same\r\n * reasoning `dev-server.ts`'s own header comment records: this module is not\r\n * exported from either package barrel and is not part of `web/package.json`'s\r\n * dependency graph — dev/CLI bootstrap only.\r\n *\r\n * Scope note: a page's\r\n * `route.path` is now composed with the `prefix` export of EVERY `layout.tsx`\r\n * on its path — outermost first (`composeRoutePath` below) — before\r\n * registration and before the collision check, so `home.page.tsx`\r\n * (`path: \"/\"`, main layout `prefix: \"/\"`) resolves to `/` and\r\n * `products.page.tsx` (`path: \"/\"`, products layout `prefix: \"/products\"`)\r\n * resolves to `/products` — no collision. A page with no `layout.tsx` on its\r\n * path composes against the implicit root prefix `\"/\"` (e.g. `/contact-us`,\r\n * `/hydration-demo`, both unaffected by composition).\r\n *\r\n * WHICH PAGES EXIST is answered by {@link discoverPageFiles}\r\n * (`web/src/build/discover-pages.ts`) — the same walk production's build\r\n * shares — so this file owns no directory-walking of its own; it serves the\r\n * page root (`<appSrcRoot>/web/**`) exactly as discovery enumerates it. WHAT\r\n * ROUTE A PAGE ANSWERS ON stays this file's own job: each page and its nearest layout are still evaluated\r\n * through Vite (`vite.ssrLoadModule`), never read statically, because a dev\r\n * page module must be the one Vite serves, warm cache and all.\r\n */\r\nimport path from \"node:path\";\r\nimport type { ViteDevServer } from \"vite\";\r\nimport {\r\n  discoverPageFiles,\r\n  ErrorPageDeclaresRouteError,\r\n  isErrorPageFile,\r\n  layoutChainFor,\r\n  toPosix,\r\n} from \"../build/discover-pages\";\r\nimport { NonLiteralRouteExportError, readRouteExports } from \"../build/read-route-exports\";\r\nimport { composeRoutePath } from \"../routing/compose-route-path\";\r\nimport { deriveFilesystemRoutePath } from \"../routing/filesystem-route\";\r\nimport { NestedLayoutsNotSupportedError, selectPageLayout } from \"../routing/layout-policy\";\r\nimport {\r\n  canonicalizeRouteExport,\r\n  resolvePageRouteCache,\r\n  resolvePageRouteName,\r\n  type PageCacheOptIn,\r\n} from \"../routing/route-identity\";\r\nimport { publishRouteTable } from \"../routing/route-table\";\r\nimport { Response, type Router } from \"@warlock.js/core\";\r\nimport { createPageRouteHandler } from \"./create-page-route-handler\";\r\nimport type { ErrorPageModule } from \"./error-page\";\r\nimport type { PipelineLoader, PipelineMiddleware } from \"./execute-page-request\";\r\nimport { isLoaderShortCircuit } from \"./settle-page-response\";\r\nimport { devHandlerStylesheetUrls } from \"./stylesheet-urls\";\r\nimport {\r\n  createNotFoundRouteHandler,\r\n  DuplicateNotFoundPageError,\r\n  isNotFoundPageFile,\r\n  NotFoundPageDeclaresRouteError,\r\n  NOT_FOUND_ROUTE_NAME,\r\n  NOT_FOUND_ROUTE_PATH,\r\n  type RegisteredRouteShape,\r\n} from \"./not-found-page\";\r\n\r\n/** Re-exported so `web/src/server/index.ts`'s existing barrel export keeps resolving. */\r\nexport { composeRoutePath };\r\n\r\nexport type PageRouteExport = string | { path: string; name?: string; cache?: PageCacheOptIn };\r\n\r\nexport type PageModuleShape = {\r\n  route?: PageRouteExport;\r\n};\r\n\r\nexport type InstalledPageRoute = {\r\n  /** The canonical declared route path, before layout-prefix composition. */\r\n  declaredPath: string;\r\n  path: string;\r\n  name: string;\r\n  file: string;\r\n  layoutFile: string | undefined;\r\n};\r\n\r\n/**\r\n * Ownership key for the framework's fallback 404 route. A NUL-prefixed value\r\n * cannot be a real filesystem path, so it cannot collide with an app page's\r\n * canonical source-file key.\r\n */\r\nexport const FRAMEWORK_DEFAULT_NOT_FOUND_SOURCE_FILE = \"\\0warlock:framework-default-404\";\r\n\r\n/**\r\n * The page's application-source-relative POSIX source path used as the router's\r\n * stable ownership key. `appSrcRoot`'s own basename preserves the existing\r\n * `src/web/...` source-file convention.\r\n */\r\nfunction canonicalSourceFileFor(pageFile: string, appSrcRoot: string): string {\r\n  return `${path.basename(appSrcRoot)}/${toPosix(path.relative(appSrcRoot, pageFile))}`;\r\n}\r\n\r\nfunction filesystemPageFileFor(pageFile: string, appSrcRoot: string): string {\r\n  return toPosix(path.relative(path.join(appSrcRoot, \"web\"), pageFile));\r\n}\r\n\r\n/**\r\n * Resolve the stable identity used to distinguish a route-export edit from an\r\n * ordinary component-body edit. The declared path is retained before layout\r\n * composition so `/settings` under `/admin` compares with the next declared\r\n * `/settings`, not with the effective `/admin/settings` route.\r\n */\r\nexport function resolvePageRouteIdentity(\r\n  routeExport: PageRouteExport | undefined,\r\n  pageFile: string,\r\n  appSrcRoot: string,\r\n): Pick<InstalledPageRoute, \"declaredPath\" | \"name\"> {\r\n  const filesystemPageFile = filesystemPageFileFor(pageFile, appSrcRoot);\r\n\r\n  if (routeExport === undefined) {\r\n    return {\r\n      declaredPath: deriveFilesystemRoutePath({ pageFile: filesystemPageFile }),\r\n      name: resolvePageRouteName(routeExport, filesystemPageFile),\r\n    };\r\n  }\r\n\r\n  return {\r\n    declaredPath: canonicalizeRouteExport(routeExport, pageFile).path,\r\n    name: resolvePageRouteName(routeExport, filesystemPageFile),\r\n  };\r\n}\r\n\r\nexport type LayoutModuleShape = {\r\n  /** Universal registration hook; invoked on this real namespace, never a composed wrapper. */\r\n  register?: () => unknown;\r\n  prefix?: string;\r\n  /**\r\n   * The default export — the thing that puts an element in the document, and\r\n   * therefore the ONLY export that decides whether a layout counts against the\r\n   * single-rendering-layout rule (`../routing/layout-policy.ts`). In dev the\r\n   * module is loaded, so this is a fact rather than a guess.\r\n   */\r\n  default?: unknown;\r\n  /** The layout's guards, in the order it declared them. */\r\n  middleware?: readonly PipelineMiddleware[];\r\n  loader?: PipelineLoader;\r\n};\r\n\r\n/** How this module gets a layout module namespace — `vite.ssrLoadModule`, in practice. */\r\ntype LoadLayout = (layoutFile: string) => Promise<LayoutModuleShape>;\r\n\r\n/**\r\n * The page's layout LEVEL, resolved from its whole chain rather than from the\r\n * one layout nearest to it.\r\n *\r\n * The render pipeline has exactly one layout slot per page\r\n * (`execute-page-request.ts`'s `PageRouteEntry[\"triple\"]`), so the chain has to\r\n * be collapsed into one module before it reaches a handler. Two things collapse\r\n * differently and both matter:\r\n *\r\n * - RENDERING is a selection: at most one layout on the chain may render, and\r\n *   the policy picks it. `renders` is read off the loaded module\r\n *   (`typeof module.default !== \"undefined\"`), never off the filename — a\r\n *   `middleware`-only layout has no default export and is not a wrapper, and\r\n *   passing a bare path to `selectPageLayout` would have it read as a rendering\r\n *   one, which is the conservative default and the wrong answer here.\r\n * - MIDDLEWARE and PREFIX are compositions: every layout on the path\r\n *   contributes, outermost first. A guard on an outer layout that the page's\r\n *   own directory knows nothing about is exactly the guard that must still run,\r\n *   and a prefix nobody composed is a URL nobody wrote down.\r\n */\r\ntype LayoutLevel = {\r\n  /** Every `layout.tsx` from the web root down to the page's directory, outermost first. */\r\n  chain: string[];\r\n  /**\r\n   * The module id the handler's layout slot is registered under, or `undefined`\r\n   * when the page has no layout at all: the layout that RENDERS, or — when none\r\n   * does — the nearest one, which is the slot dev has always used and so the\r\n   * choice that changes nothing but the middleware for a chain with no wrapper\r\n   * in it.\r\n   */\r\n  layoutFile: string | undefined;\r\n  /** Every layout's `prefix`, composed outermost first — `discoverPages`' own reduction. */\r\n  prefix: string;\r\n  /** Declared prefixes keyed by layout directory relative to this page's web root. */\r\n  prefixesByDirectory: Readonly<Record<string, string>>;\r\n};\r\n\r\nasync function resolveLayoutLevel(\r\n  pageFile: string,\r\n  webRoot: string,\r\n  loadLayout: LoadLayout,\r\n): Promise<LayoutLevel> {\r\n  const chain = layoutChainFor(pageFile, webRoot);\r\n  const modules = await Promise.all(chain.map(loadLayout));\r\n  const selection = selectPageLayout(\r\n    chain.map((layout, index) => ({\r\n      layout,\r\n      renders: typeof modules[index].default !== \"undefined\",\r\n    })),\r\n  );\r\n\r\n  if (selection.type === \"rejected\") {\r\n    throw new NestedLayoutsNotSupportedError(pageFile, selection.layouts);\r\n  }\r\n\r\n  return {\r\n    chain,\r\n    layoutFile: selection.type === \"selected\" ? selection.layout : chain.at(-1),\r\n    prefix: modules.reduce(\r\n      (composed, layoutModule) => composeRoutePath(composed, layoutModule.prefix ?? \"/\"),\r\n      \"/\",\r\n    ),\r\n    prefixesByDirectory: Object.fromEntries(\r\n      chain.flatMap((layoutFile, index) => {\r\n        const prefix = modules[index].prefix;\r\n\r\n        return prefix === undefined\r\n          ? []\r\n          : [[toPosix(path.relative(webRoot, path.dirname(layoutFile))), prefix]];\r\n      }),\r\n    ),\r\n  };\r\n}\r\n\r\n/**\r\n * The layout slot's module for ONE request: the slot host's own namespace, with\r\n * the whole chain's middleware in place of its own — outermost first, which is\r\n * the order stage 3 runs the array in (`execute-page-request.ts:519-524`) and\r\n * the order an outer `optionalAuth` needs in order to have resolved an identity\r\n * before an inner `gate()` checks it.\r\n *\r\n * Loaded per call, not once at install time: a dev layout module must be the\r\n * one Vite is currently serving, edits and all.\r\n */\r\nasync function composeLayoutLevel(\r\n  level: LayoutLevel & { layoutFile: string },\r\n  loadLayout: LoadLayout,\r\n): Promise<LayoutModuleShape> {\r\n  const modules = await Promise.all(level.chain.map(loadLayout));\r\n  const hostIndex = level.chain.indexOf(level.layoutFile);\r\n  const host = modules[hostIndex];\r\n\r\n  return {\r\n    ...host,\r\n    middleware: modules.flatMap((layoutModule) => [...(layoutModule.middleware ?? [])]),\r\n    loader: async (context) => {\r\n      let hostData: unknown;\r\n\r\n      for (let index = 0; index < modules.length; index++) {\r\n        const value = await modules[index].loader?.(context);\r\n\r\n        if (value instanceof Response || isLoaderShortCircuit(value)) return value;\r\n        if (index === hostIndex) hostData = value;\r\n      }\r\n\r\n      return hostData;\r\n    },\r\n  };\r\n}\r\n\r\nexport type InstallPageRoutesOptions = {\r\n  router: Router;\r\n  vite: ViteDevServer;\r\n  /** v5/app/src — pages live under \"<appSrcRoot>/web/**\". */\r\n  appSrcRoot: string;\r\n  /** v5/app/src/web/root.tsx — the single global app-root file. */\r\n  appFile: string;\r\n  /**\r\n   * The application root Vite's dev server serves from — `dev-server.ts`'s\r\n   * `paths.appRoot`, i.e. `<appRoot>/src === appSrcRoot` by default. Every\r\n   * handler's stylesheet URLs are expressed relative to THIS, because that is\r\n   * the root Vite's dev server actually resolves `/…` URLs against\r\n   * (`stylesheet-urls.ts`'s `devStylesheetUrls`) — not `appSrcRoot`, which is\r\n   * one directory level in.\r\n   *\r\n   * OPTIONAL and defaulted to `path.dirname(appSrcRoot)`: the caller that\r\n   * wires dev boot (`web-connector.ts`) does not pass this field today, and\r\n   * that default is exactly the relationship it constructs `appSrcRoot` from\r\n   * (`appSrcRoot = path.join(appRoot, \"src\")`) — correct for every actual\r\n   * deployment, and overridable by a caller with a non-default layout.\r\n   */\r\n  appRoot?: string;\r\n  /** Browser module loaded after the server-rendered application and payload. */\r\n  hydrationClientModuleUrl?: string;\r\n  /**\r\n   * UNUSED. Retained on this type only because `web-connector.ts` still builds\r\n   * an options object naming it (`devStylesheetUrls(paths.appRoot,\r\n   * paths.appFile)`, computed once for the whole application). Each handler\r\n   * now computes its OWN stylesheet chain — `[root, ...outer-to-inner matched\r\n   * layouts, page]`, via `devHandlerStylesheetUrls` — inside the registration\r\n   * loop below, because a single application-wide list cannot express \"this\r\n   * page's own CSS\" without also carrying every other page's.\r\n   */\r\n  stylesheetUrls?: readonly string[];\r\n  /** Same helper `dev-server.ts` exports — passed in, not imported, to avoid a dev-server.ts <-> this-file cycle. */\r\n};\r\n\r\n/**\r\n * Registers every discoverable page into `options.router`. Throws\r\n * IMMEDIATELY, naming both files, the moment two pages declare the same\r\n * `route.path` — a registration-time failure, not a runtime 404 one of them\r\n * silently loses.\r\n *\r\n * Pages with no `route` export derive their path and name from their location\r\n * below `src/web`, using the same pure filesystem-routing helper as the build.\r\n */\r\nexport async function installPageRoutes(\r\n  options: InstallPageRoutesOptions,\r\n): Promise<InstalledPageRoute[]> {\r\n  const { router, vite, appSrcRoot, appFile, hydrationClientModuleUrl } = options;\r\n  // See `InstallPageRoutesOptions.appRoot` for why this default, not\r\n  // `appSrcRoot` itself, is the root every handler's CSS is resolved against.\r\n  const stylesheetRoot = options.appRoot ?? path.dirname(appSrcRoot);\r\n  const discovered = [...discoverPageFiles(appSrcRoot)].sort((left, right) =>\r\n    left.pageFile < right.pageFile ? -1 : left.pageFile > right.pageFile ? 1 : 0,\r\n  );\r\n\r\n  // THE NOT-FOUND PAGE IS TAKEN OUT OF THE ORDINARY LOOP, not filtered inside\r\n  // it. It has no `route` export to read, no path to compose and no collision\r\n  // to check — every step below is about a page with a URL, and `404.page.tsx`\r\n  // does not have one. Registering it here would put it at `/404`, which is not\r\n  // a page anybody asked to be able to visit.\r\n  const errorPageFiles = discovered.filter((page) => isErrorPageFile(page.pageFile));\r\n  const notFoundPageFiles = discovered.filter((page) => isNotFoundPageFile(page.pageFile));\r\n  const pageFiles = discovered.filter(\r\n    (page) => !isNotFoundPageFile(page.pageFile) && !isErrorPageFile(page.pageFile),\r\n  );\r\n\r\n  if (errorPageFiles.length > 1) {\r\n    throw new Error(\r\n      `Two error pages were found: ${errorPageFiles.map((page) => page.pageFile).join(\", \")}.`,\r\n    );\r\n  }\r\n\r\n  const errorPageFile = errorPageFiles[0]?.pageFile;\r\n\r\n  // Parse only: the error boundary must remain lazy until a request actually\r\n  // fails, while a route export is still rejected at install time.\r\n  if (errorPageFile !== undefined) {\r\n    const declarations = readRouteExports(errorPageFile);\r\n    if (!declarations.ok) throw new NonLiteralRouteExportError(declarations.rejection);\r\n    if (declarations.route !== undefined) throw new ErrorPageDeclaresRouteError(errorPageFile);\r\n  }\r\n  const loadErrorPage =\r\n    errorPageFile === undefined\r\n      ? undefined\r\n      : () => vite.ssrLoadModule(errorPageFile) as Promise<ErrorPageModule>;\r\n\r\n  if (notFoundPageFiles.length > 1) {\r\n    throw new DuplicateNotFoundPageError(notFoundPageFiles.map((page) => page.pageFile));\r\n  }\r\n\r\n  const installed: InstalledPageRoute[] = [];\r\n  const fileByPath = new Map<string, string>();\r\n\r\n  for (const { pageFile, webRoot } of pageFiles) {\r\n    const pageModule = (await vite.ssrLoadModule(pageFile)) as PageModuleShape;\r\n\r\n    const sourceFile = canonicalSourceFileFor(pageFile, appSrcRoot);\r\n\r\n    // Route identity is explicit when declared and filesystem-derived otherwise.\r\n    const { declaredPath: routePath, name } = resolvePageRouteIdentity(\r\n      pageModule.route,\r\n      pageFile,\r\n      appSrcRoot,\r\n    );\r\n\r\n    // Validated at INSTALL time, with everything else — a malformed `cache`\r\n    // opt-in fails boot, not the first request that would have served it.\r\n    const cache = resolvePageRouteCache(pageModule.route, pageFile);\r\n\r\n    const loadLayout: LoadLayout = (layoutFile) =>\r\n      vite.ssrLoadModule(layoutFile) as Promise<LayoutModuleShape>;\r\n    const layoutLevel = await resolveLayoutLevel(pageFile, webRoot, loadLayout);\r\n    const { layoutFile, prefix: layoutPrefix } = layoutLevel;\r\n\r\n    const effectivePath =\r\n      pageModule.route === undefined\r\n        ? deriveFilesystemRoutePath({\r\n            pageFile: filesystemPageFileFor(pageFile, appSrcRoot),\r\n            layoutPrefixes: layoutLevel.prefixesByDirectory,\r\n          })\r\n        : composeRoutePath(layoutPrefix, routePath);\r\n\r\n    const existingFile = fileByPath.get(effectivePath);\r\n\r\n    if (existingFile) {\r\n      throw new Error(\r\n        `installPageRoutes: composed route path \"${effectivePath}\" (layout ` +\r\n          `prefix \"${layoutPrefix}\" + route.path \"${routePath}\") is declared by two ` +\r\n          `pages (web/src/server/install-page-routes.ts) — \"${existingFile}\" and ` +\r\n          `\"${pageFile}\". Every page's composed route path must be unique.`,\r\n      );\r\n    }\r\n\r\n    fileByPath.set(effectivePath, pageFile);\r\n\r\n    // Every registered handler gets ITS OWN immutable, ordered, deduped CSS\r\n    // chain: root, then every matched layout outer to inner\r\n    // (`layoutLevel.chain`), then the page — the same order the render\r\n    // pipeline loads that chain in, so cascade order matches load order.\r\n    // Computed once here, at registration, not per request: dev re-registers\r\n    // on every restart, so a stale chain cannot outlive the source edit that\r\n    // changed it.\r\n    const stylesheetUrls = devHandlerStylesheetUrls(stylesheetRoot, [\r\n      appFile,\r\n      ...layoutLevel.chain,\r\n      pageFile,\r\n    ]);\r\n\r\n    await router.withSourceFile(sourceFile, () =>\r\n      router.get(\r\n        effectivePath,\r\n        // The handler itself is `createPageRouteHandler`\r\n        // (`web/src/server/create-page-route-handler.ts`) — a named seam a\r\n        // future `type: \"page\"` route can bind to, and testable without a Vite\r\n        // server. Vite appears here only as the dev answer to \"how do I load a\r\n        // module\"; the handler takes that as an input and knows nothing else\r\n        // about it.\r\n        createPageRouteHandler({\r\n          path: effectivePath,\r\n          name,\r\n          appFile,\r\n          pageFile,\r\n          layoutFile,\r\n          // The layout slot's id resolves to the COMPOSED level — every layout's\r\n          // middleware, in chain order — and every other id goes straight to\r\n          // Vite. A one-layout chain has nothing to compose, so it is left to\r\n          // resolve as the exact module Vite hands back, untouched.\r\n          loadModule:\r\n            layoutLevel.chain.length > 1 && layoutFile !== undefined\r\n              ? (moduleId) =>\r\n                  moduleId === layoutFile\r\n                    ? composeLayoutLevel({ ...layoutLevel, layoutFile }, loadLayout)\r\n                    : vite.ssrLoadModule(moduleId)\r\n              : (moduleId) => vite.ssrLoadModule(moduleId),\r\n          // Registration tracks real module namespaces, not the composed\r\n          // layout wrapper above. Loading the raw chain per request also lets\r\n          // Vite hand over a replacement namespace after an HMR update; the\r\n          // helper's WeakSet then gives that new identity its one invocation.\r\n          loadRegistrationLayouts: () => Promise.all(layoutLevel.chain.map(loadLayout)),\r\n          hydrationClientModuleUrl,\r\n          loadErrorPage,\r\n          stylesheetUrls,\r\n          cache,\r\n        }),\r\n        // `isPage` marks this route as SSR-served. Pages and API routes share one\r\n        // router and one route-name namespace, so the router's duplicate-name\r\n        // error reads this flag to say which claimant is the page.\r\n        { name, isPage: true },\r\n      ),\r\n    );\r\n\r\n    installed.push({\r\n      declaredPath: routePath,\r\n      path: effectivePath,\r\n      name,\r\n      file: pageFile,\r\n      layoutFile,\r\n    });\r\n  }\r\n\r\n  /*\r\n    THE CATCH-ALL, registered LAST and only when this application has a page\r\n    surface at all. \"Configured with web, no pages yet\" is a legal state, and an\r\n    application serving no pages has no page 404 to answer with — its unmatched\r\n    URLs stay core's to answer, exactly as they are today.\r\n\r\n    Registered even when the application ships no `404.page.tsx`: the framework\r\n    default still answers 404, so an application that has not written one yet\r\n    gets the right STATUS from the first request, and adding the file later\r\n    changes the body and nothing else.\r\n  */\r\n  if (pageFiles.length > 0 || notFoundPageFiles.length > 0) {\r\n    const notFoundPageFile = notFoundPageFiles[0]?.pageFile;\r\n\r\n    // Read at INSTALL time, so a `route` export on the not-found page is\r\n    // refused at boot with everything else — not on the first request that\r\n    // misses, which is the one request nobody is watching.\r\n    if (notFoundPageFile !== undefined) {\r\n      const notFoundModule = (await vite.ssrLoadModule(notFoundPageFile)) as PageModuleShape;\r\n\r\n      if (notFoundModule.route !== undefined) {\r\n        throw new NotFoundPageDeclaresRouteError(notFoundPageFile);\r\n      }\r\n    }\r\n\r\n    const registerNotFoundRoute = () =>\r\n      router.get(\r\n        NOT_FOUND_ROUTE_PATH,\r\n        createNotFoundRouteHandler({\r\n          renderPage:\r\n            notFoundPageFile === undefined\r\n              ? undefined\r\n              : createPageRouteHandler({\r\n                  path: NOT_FOUND_ROUTE_PATH,\r\n                  name: NOT_FOUND_ROUTE_NAME,\r\n                  appFile,\r\n                  pageFile: notFoundPageFile,\r\n                  // NO LAYOUT, deliberately, and it is the same trade as \"no\r\n                  // loader on the 404 page\": a layout brings its whole chain's\r\n                  // middleware with it, and a guard that redirects or throws on\r\n                  // the not-found path turns a missing page into an incident. The\r\n                  // page renders inside the application root and nothing else.\r\n                  layoutFile: undefined,\r\n                  loadModule: (moduleId) => vite.ssrLoadModule(moduleId),\r\n                  hydrationClientModuleUrl,\r\n                  loadErrorPage,\r\n                  // NO LAYOUT means no layout CSS either — just root and the\r\n                  // not-found page's own stylesheets, same reasoning as above.\r\n                  stylesheetUrls: devHandlerStylesheetUrls(stylesheetRoot, [\r\n                    appFile,\r\n                    notFoundPageFile,\r\n                  ]),\r\n                  // The URL that missed IS this route's pattern for this request.\r\n                  matchPath: (requestPath) => requestPath,\r\n                  statusForRenderedOk: 404,\r\n                  skipPageLoader: true,\r\n                }),\r\n        }),\r\n        // `isPage` for the same reason every other page route carries it: the\r\n        // router's duplicate-name error reads the flag to say which claimant is\r\n        // the page.\r\n        { name: NOT_FOUND_ROUTE_NAME, isPage: true },\r\n      );\r\n\r\n    if (notFoundPageFile === undefined) {\r\n      await router.withSourceFile(FRAMEWORK_DEFAULT_NOT_FOUND_SOURCE_FILE, registerNotFoundRoute);\r\n    } else {\r\n      await router.withSourceFile(\r\n        canonicalSourceFileFor(notFoundPageFile, appSrcRoot),\r\n        registerNotFoundRoute,\r\n      );\r\n    }\r\n  }\r\n\r\n  /*\r\n    Published from the SAME loop that registered the routes, so `href()` and the\r\n    router cannot disagree about where a name points. It happens here rather\r\n    than in the caller because a caller that forgets leaves every `<Link>` on\r\n    the server throwing at render — and dev republishes on every restart, which\r\n    is why the table replaces wholesale instead of merging: a deleted page's\r\n    name has to stop resolving.\r\n  */\r\n  publishRouteTable(installed, \"installPageRoutes (dev)\");\r\n\r\n  return installed;\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA2FA,MAAa,0CAA0C;;;;;;AAOvD,SAAS,uBAAuB,UAAkB,YAA4B;CAC5E,OAAO,GAAG,KAAK,SAAS,UAAU,EAAE,GAAG,QAAQ,KAAK,SAAS,YAAY,QAAQ,CAAC;AACpF;AAEA,SAAS,sBAAsB,UAAkB,YAA4B;CAC3E,OAAO,QAAQ,KAAK,SAAS,KAAK,KAAK,YAAY,KAAK,GAAG,QAAQ,CAAC;AACtE;;;;;;;AAQA,SAAgB,yBACd,aACA,UACA,YACmD;CACnD,MAAM,qBAAqB,sBAAsB,UAAU,UAAU;CAErE,IAAI,gBAAgB,QAClB,OAAO;EACL,cAAc,0BAA0B,EAAE,UAAU,mBAAmB,CAAC;EACxE,MAAM,qBAAqB,aAAa,kBAAkB;CAC5D;CAGF,OAAO;EACL,cAAc,wBAAwB,aAAa,QAAQ,CAAC,CAAC;EAC7D,MAAM,qBAAqB,aAAa,kBAAkB;CAC5D;AACF;AA0DA,eAAe,mBACb,UACA,SACA,YACsB;CACtB,MAAM,QAAQ,eAAe,UAAU,OAAO;CAC9C,MAAM,UAAU,MAAM,QAAQ,IAAI,MAAM,IAAI,UAAU,CAAC;CACvD,MAAM,YAAY,iBAChB,MAAM,KAAK,QAAQ,WAAW;EAC5B;EACA,SAAS,OAAO,QAAQ,MAAM,CAAC,YAAY;CAC7C,EAAE,CACJ;CAEA,IAAI,UAAU,SAAS,YACrB,MAAM,IAAI,+BAA+B,UAAU,UAAU,OAAO;CAGtE,OAAO;EACL;EACA,YAAY,UAAU,SAAS,aAAa,UAAU,SAAS,MAAM,GAAG,EAAE;EAC1E,QAAQ,QAAQ,QACb,UAAU,iBAAiB,iBAAiB,UAAU,aAAa,UAAU,GAAG,GACjF,GACF;EACA,qBAAqB,OAAO,YAC1B,MAAM,SAAS,YAAY,UAAU;GACnC,MAAM,SAAS,QAAQ,MAAM,CAAC;GAE9B,OAAO,WAAW,SACd,CAAC,IACD,CAAC,CAAC,QAAQ,KAAK,SAAS,SAAS,KAAK,QAAQ,UAAU,CAAC,CAAC,GAAG,MAAM,CAAC;EAC1E,CAAC,CACH;CACF;AACF;;;;;;;;;;;AAYA,eAAe,mBACb,OACA,YAC4B;CAC5B,MAAM,UAAU,MAAM,QAAQ,IAAI,MAAM,MAAM,IAAI,UAAU,CAAC;CAC7D,MAAM,YAAY,MAAM,MAAM,QAAQ,MAAM,UAAU;CAGtD,OAAO;EACL,GAHW,QAAQ;EAInB,YAAY,QAAQ,SAAS,iBAAiB,CAAC,GAAI,aAAa,cAAc,CAAC,CAAE,CAAC;EAClF,QAAQ,OAAO,YAAY;GACzB,IAAI;GAEJ,KAAK,IAAI,QAAQ,GAAG,QAAQ,QAAQ,QAAQ,SAAS;IACnD,MAAM,QAAQ,MAAM,QAAQ,MAAM,CAAC,SAAS,OAAO;IAEnD,IAAI,iBAAiB,YAAY,qBAAqB,KAAK,GAAG,OAAO;IACrE,IAAI,UAAU,WAAW,WAAW;GACtC;GAEA,OAAO;EACT;CACF;AACF;;;;;;;;;;AAgDA,eAAsB,kBACpB,SAC+B;CAC/B,MAAM,EAAE,QAAQ,MAAM,YAAY,SAAS,6BAA6B;CAGxE,MAAM,iBAAiB,QAAQ,WAAW,KAAK,QAAQ,UAAU;CACjE,MAAM,aAAa,CAAC,GAAG,kBAAkB,UAAU,CAAC,CAAC,CAAC,MAAM,MAAM,UAChE,KAAK,WAAW,MAAM,WAAW,KAAK,KAAK,WAAW,MAAM,WAAW,IAAI,CAC7E;CAOA,MAAM,iBAAiB,WAAW,QAAQ,SAAS,gBAAgB,KAAK,QAAQ,CAAC;CACjF,MAAM,oBAAoB,WAAW,QAAQ,SAAS,mBAAmB,KAAK,QAAQ,CAAC;CACvF,MAAM,YAAY,WAAW,QAC1B,SAAS,CAAC,mBAAmB,KAAK,QAAQ,KAAK,CAAC,gBAAgB,KAAK,QAAQ,CAChF;CAEA,IAAI,eAAe,SAAS,GAC1B,MAAM,IAAI,MACR,+BAA+B,eAAe,KAAK,SAAS,KAAK,QAAQ,CAAC,CAAC,KAAK,IAAI,EAAE,EACxF;CAGF,MAAM,gBAAgB,eAAe,EAAE,EAAE;CAIzC,IAAI,kBAAkB,QAAW;EAC/B,MAAM,eAAe,iBAAiB,aAAa;EACnD,IAAI,CAAC,aAAa,IAAI,MAAM,IAAI,2BAA2B,aAAa,SAAS;EACjF,IAAI,aAAa,UAAU,QAAW,MAAM,IAAI,4BAA4B,aAAa;CAC3F;CACA,MAAM,gBACJ,kBAAkB,SACd,eACM,KAAK,cAAc,aAAa;CAE5C,IAAI,kBAAkB,SAAS,GAC7B,MAAM,IAAI,2BAA2B,kBAAkB,KAAK,SAAS,KAAK,QAAQ,CAAC;CAGrF,MAAM,YAAkC,CAAC;CACzC,MAAM,6BAAa,IAAI,IAAoB;CAE3C,KAAK,MAAM,EAAE,UAAU,aAAa,WAAW;EAC7C,MAAM,aAAc,MAAM,KAAK,cAAc,QAAQ;EAErD,MAAM,aAAa,uBAAuB,UAAU,UAAU;EAG9D,MAAM,EAAE,cAAc,WAAW,SAAS,yBACxC,WAAW,OACX,UACA,UACF;EAIA,MAAM,QAAQ,sBAAsB,WAAW,OAAO,QAAQ;EAE9D,MAAM,cAA0B,eAC9B,KAAK,cAAc,UAAU;EAC/B,MAAM,cAAc,MAAM,mBAAmB,UAAU,SAAS,UAAU;EAC1E,MAAM,EAAE,YAAY,QAAQ,iBAAiB;EAE7C,MAAM,gBACJ,WAAW,UAAU,SACjB,0BAA0B;GACxB,UAAU,sBAAsB,UAAU,UAAU;GACpD,gBAAgB,YAAY;EAC9B,CAAC,IACD,iBAAiB,cAAc,SAAS;EAE9C,MAAM,eAAe,WAAW,IAAI,aAAa;EAEjD,IAAI,cACF,MAAM,IAAI,MACR,2CAA2C,cAAc,oBAC5C,aAAa,kBAAkB,UAAU,yEACA,aAAa,SAC7D,SAAS,oDACjB;EAGF,WAAW,IAAI,eAAe,QAAQ;EAStC,MAAM,iBAAiB,yBAAyB,gBAAgB;GAC9D;GACA,GAAG,YAAY;GACf;EACF,CAAC;EAED,MAAM,OAAO,eAAe,kBAC1B,OAAO,IACL,eAOA,uBAAuB;GACrB,MAAM;GACN;GACA;GACA;GACA;GAKA,YACE,YAAY,MAAM,SAAS,KAAK,eAAe,UAC1C,aACC,aAAa,aACT,mBAAmB;IAAE,GAAG;IAAa;GAAW,GAAG,UAAU,IAC7D,KAAK,cAAc,QAAQ,KAChC,aAAa,KAAK,cAAc,QAAQ;GAK/C,+BAA+B,QAAQ,IAAI,YAAY,MAAM,IAAI,UAAU,CAAC;GAC5E;GACA;GACA;GACA;EACF,CAAC,GAID;GAAE;GAAM,QAAQ;EAAK,CACvB,CACF;EAEA,UAAU,KAAK;GACb,cAAc;GACd,MAAM;GACN;GACA,MAAM;GACN;EACF,CAAC;CACH;CAaA,IAAI,UAAU,SAAS,KAAK,kBAAkB,SAAS,GAAG;EACxD,MAAM,mBAAmB,kBAAkB,EAAE,EAAE;EAK/C,IAAI,qBAAqB,QAGvB;QAAI,MAF0B,KAAK,cAAc,gBAAgB,EAE/C,CAAC,UAAU,QAC3B,MAAM,IAAI,+BAA+B,gBAAgB;EAC3D;EAGF,MAAM,8BACJ,OAAO,SAEL,2BAA2B,EACzB,YACE,qBAAqB,SACjB,SACA,uBAAuB;GACrB;GACA,MAAM;GACN;GACA,UAAU;GAMV,YAAY;GACZ,aAAa,aAAa,KAAK,cAAc,QAAQ;GACrD;GACA;GAGA,gBAAgB,yBAAyB,gBAAgB,CACvD,SACA,gBACF,CAAC;GAED,YAAY,gBAAgB;GAC5B,qBAAqB;GACrB,gBAAgB;EAClB,CAAC,EACT,CAAC,GAID;GAAE,MAAM;GAAsB,QAAQ;EAAK,CAC7C;EAEF,IAAI,qBAAqB,QACvB,MAAM,OAAO,eAAe,yCAAyC,qBAAqB;OAE1F,MAAM,OAAO,eACX,uBAAuB,kBAAkB,UAAU,GACnD,qBACF;CAEJ;CAUA,kBAAkB,WAAW,yBAAyB;CAEtD,OAAO;AACT"}

package/esm/server/not-found-page.d.mts

@@ -87,19 +87,7 @@ declare function classifyUnmatchedRequest(input: {
   method: string;
   accept: string | undefined;
 }): UnmatchedRequestKind;
-/**
- * The document served when the application ships no `404.page.tsx`.
- *
- * Deliberately a STRING, not a React render: it must survive the case where the
- * application root, a layout or the page module is exactly what is broken, and
- * a default that can itself fail is not a default. It carries no stylesheet and
- * no hydration script for the same reason — nothing here can 500.
- *
- * It answers 404 like the real page does, because the status is the part that
- * search engines, caches and monitoring read; a framework default that soft-404s
- * would teach every un-customised application to lie.
- */
-declare function frameworkDefaultNotFoundDocument(): string;
+declare function frameworkDefaultNotFoundDocument(locale?: string): string;
 type NotFoundRouteHandlerOptions = {
   /**
    * The application's `404.page.tsx`, already built into a page handler by

package/esm/server/not-found-page.mjs

@@ -1,3 +1,5 @@
+import { buildFrameworkDefaultNotFoundStylesheetUrl } from "./framework-default-not-found-stylesheet.mjs";
+
 //#region ../web/src/server/not-found-page.ts
 /**
 * The one filename that makes a page THE not-found page.
@@ -111,15 +113,57 @@ function classifyUnmatchedRequest(input) {
 *
 * Deliberately a STRING, not a React render: it must survive the case where the
 * application root, a layout or the page module is exactly what is broken, and
-* a default that can itself fail is not a default. It carries no stylesheet and
-* no hydration script for the same reason — nothing here can 500.
+* a default that can itself fail is not a default. Its stylesheet is embedded in
+* the document as a data URL, and it carries no hydration script, so serving the
+* fallback requires no application render and no follow-up fetch.
 *
 * It answers 404 like the real page does, because the status is the part that
 * search engines, caches and monitoring read; a framework default that soft-404s
 * would teach every un-customised application to lie.
 */
-function frameworkDefaultNotFoundDocument() {
-	return `<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><meta name="robots" content="noindex"><title>404 — Page not found</title></head><body><h1>404 — Page not found</h1><p>This URL does not match any page.</p><p>To replace this page, add <code>${NOT_FOUND_PAGE_FILENAME}</code> to a web folder (for example <code>src/web/404.page.tsx</code>).</p></body></html>`;
+function resolveDefaultNotFoundDocumentLocale(locale) {
+	const fallback = {
+		lang: "en",
+		dir: "ltr"
+	};
+	if (typeof locale !== "string" || locale.trim() === "") return fallback;
+	try {
+		const Locale = Intl.Locale;
+		if (typeof Locale !== "function") return fallback;
+		const resolvedLocale = new Locale(locale);
+		const lang = resolvedLocale.toString();
+		const textInfo = resolvedLocale.textInfo;
+		if (typeof textInfo !== "object" || textInfo === null) return fallback;
+		const direction = textInfo.direction;
+		if (direction !== "ltr" && direction !== "rtl") return fallback;
+		return {
+			lang,
+			dir: direction
+		};
+	} catch {
+		return fallback;
+	}
+}
+function frameworkDefaultNotFoundDocument(locale) {
+	const { lang, dir } = resolveDefaultNotFoundDocumentLocale(locale);
+	return `<!doctype html>
+<html lang="${lang}" dir="${dir}">
+<head>
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <meta name="robots" content="noindex">
+  <title>404 | Warlock</title>
+  <link rel="stylesheet" href="${buildFrameworkDefaultNotFoundStylesheetUrl()}">
+</head>
+<body>
+  <main>
+    <div class="rule" aria-hidden="true"></div>
+    <h1>404</h1>
+    <p dir="auto">This page is outside the spellbook.</p>
+    <a href="/" dir="auto">Return home</a>
+  </main>
+</body>
+</html>`;
 }
 /**
 * The handler registered on the catch-all.
@@ -132,6 +176,7 @@ function createNotFoundRouteHandler(options) {
 	const { renderPage } = options;
 	return async (context) => {
 		const { request, response } = context;
+		response.header("Cache-Control", "no-store");
 		const accept = request.header("accept");
 		if (classifyUnmatchedRequest({
 			method: request.method,
@@ -145,7 +190,7 @@ function createNotFoundRouteHandler(options) {
 			return;
 		}
 		if (renderPage === void 0) {
-			await response.html(frameworkDefaultNotFoundDocument(), 404);
+			await response.html(frameworkDefaultNotFoundDocument(request.locale), 404);
 			return;
 		}
 		return renderPage(context);