@warlock.js/web 5.4.0 → 5.6.0

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

@@ -1,14 +1,15 @@
 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 { duplicateRoutePathMessage } from "../routing/duplicate-route-path.mjs";
 import { deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
-import { NestedLayoutsNotSupportedError, selectPageLayout } from "../routing/layout-policy.mjs";
-import { canonicalizeRouteExport, resolvePageRouteCache, resolvePageRouteName } from "../routing/route-identity.mjs";
+import { resolveLayoutLevel } from "../routing/layout-level.mjs";
+import { resolvePageRouteCache, resolvePageRouteIdentity } from "../routing/route-identity.mjs";
 import { createPageRouteHandler } from "./create-page-route-handler.mjs";
+import { foldLayoutLoaders } from "./fold-layout-loaders.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";
-import { Response } from "@warlock.js/core";
+import "@warlock.js/core";
 
 //#region ../web/src/server/install-page-routes-from-manifest.ts
 /**
@@ -26,10 +27,13 @@ import { Response } from "@warlock.js/core";
 * and the guards that run before it renders. A page's `route` export and the
 * `prefix` and `middleware` exports of EVERY layout on its path are read off the
 * module namespaces here, at boot, and composed by the same rules dev composes
-* them by ({@link layoutLevelOf}, {@link composeLayoutLevel}) — so the URL a page
-* answers on and the chain that guards it are decided by the page's own source
-* in both modes, and a build cannot quietly disagree with the dev server about
-* either.
+* them by — a shared mechanism now, not a promise: {@link layoutLevelOf} calls
+* `../routing/layout-level.ts`'s `resolveLayoutLevel`, the same selection and
+* prefix-composition rule dev's own `resolveLayoutLevel` calls, and
+* {@link composeLayoutLevel} folds loaders through the same
+* `./fold-layout-loaders.ts` dev's does — so the URL a page answers on and the
+* chain that guards it are decided by the page's own source in both modes, and
+* a build cannot quietly disagree with the dev server about either.
 *
 * WHAT IS DELIBERATELY DIFFERENT: this is synchronous. Every module is already
 * in memory, so registration has nothing to await; the loader handed to each
@@ -42,30 +46,29 @@ import { Response } from "@warlock.js/core";
 * app-root-relative (`"src/web/..."`, `page-manifest.ts`'s own doc comment),
 * so dropping the first two segments — `<srcDir>`, then the literal `"web"` —
 * recovers exactly what `deriveFilesystemRoutePath`/`deriveFilesystemRouteName`
-* expect: the same value dev computes as `filesystemPageFileFor`
-* (`install-page-routes.ts:101-103`).
+* expect: the same value dev computes as `install-page-routes.ts`'s
+* `filesystemPageFileFor`.
 */
 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. */
+/**
+* Exported for `../routing/route-name-parity.spec.ts`, which proves this and
+* dev's own call agree — both now call the same `../routing/route-identity.ts`
+* `resolvePageRouteIdentity`, so this wrapper's only job is supplying THIS
+* installer's identifiers: the manifest `sourceFile` doubles as the
+* `route.path` rejection context, and its web-root-relative form is the
+* filesystem-derivation input.
+*/
 function resolveRoute(routeExport, sourceFile) {
-	const pageFile = webRelativeSourceFile(sourceFile);
-	if (routeExport === void 0) return {
-		path: deriveFilesystemRoutePath({ pageFile }),
-		name: resolvePageRouteName(routeExport, pageFile)
-	};
-	return {
-		path: canonicalizeRouteExport(routeExport, sourceFile).path,
-		name: resolvePageRouteName(routeExport, pageFile)
-	};
+	return resolvePageRouteIdentity(routeExport, webRelativeSourceFile(sourceFile), sourceFile);
 }
 /**
 * Every layout's declared `prefix`, keyed by its directory relative to the
-* web root — the same table dev builds as `LayoutLevel.prefixesByDirectory`
-* (`install-page-routes.ts:214-222`) and the one
-* {@link deriveFilesystemRoutePath} uses to let a directory's own layout
-* rename the URL segment a bare directory name would otherwise contribute.
+* web root — the same table dev builds as its own `LayoutLevel.prefixesByDirectory`,
+* and the one {@link deriveFilesystemRoutePath} uses to let a directory's own
+* layout rename the URL segment a bare directory name would otherwise
+* contribute.
 */
 function layoutPrefixesOf(page) {
 	return Object.fromEntries(page.layouts.flatMap((layout) => {
@@ -77,14 +80,14 @@ function layoutPrefixesOf(page) {
 	}));
 }
 function layoutLevelOf(page) {
-	const selection = selectPageLayout(page.layouts.map((layout) => ({
-		layout: layout.sourceFile,
-		renders: typeof layout.module.default !== "undefined"
+	const level = resolveLayoutLevel(page.sourceFile, page.layouts.map((layout) => ({
+		id: layout.sourceFile,
+		renders: typeof layout.module.default !== "undefined",
+		prefix: layout.module.prefix
 	})));
-	if (selection.type === "rejected") throw new NestedLayoutsNotSupportedError(page.sourceFile, selection.layouts);
 	return {
-		host: selection.type === "selected" ? page.layouts.find((layout) => layout.sourceFile === selection.layout) : page.layouts.at(-1),
-		prefix: page.layouts.reduce((composed, layout) => composeRoutePath(composed, layout.module.prefix ?? "/"), "/")
+		host: page.layouts.find((layout) => layout.sourceFile === level.hostId),
+		prefix: level.prefix
 	};
 }
 /**
@@ -106,15 +109,7 @@ function composeLayoutLevel(page, host) {
 	return {
 		...host.module,
 		middleware: page.layouts.flatMap((layout) => [...layout.module.middleware ?? []]),
-		loader: async (context) => {
-			let hostData;
-			for (let index = 0; index < page.layouts.length; index++) {
-				const value = await page.layouts[index].module.loader?.(context);
-				if (value instanceof Response || isLoaderShortCircuit(value)) return value;
-				if (index === hostIndex) hostData = value;
-			}
-			return hostData;
-		}
+		loader: foldLayoutLoaders(page.layouts.map((layout) => layout.module.loader), hostIndex)
 	};
 }
 /**
@@ -155,7 +150,15 @@ function installPageRoutesFromManifest(options) {
 			layoutPrefixes: layoutPrefixesOf(page)
 		}) : composeRoutePath(layoutPrefix, routePath);
 		const existingFile = fileByPath.get(effectivePath);
-		if (existingFile) throw new Error(`installPageRoutesFromManifest: composed route path "${effectivePath}" (layout prefix "${layoutPrefix}" + route.path "${routePath}") is declared by two pages — "${existingFile}" and "${page.sourceFile}". Every page's composed route path must be unique.`);
+		if (existingFile) throw new Error(duplicateRoutePathMessage({
+			effectivePath,
+			existingFile,
+			newFile: page.sourceFile,
+			composition: {
+				layoutPrefix,
+				routePath
+			}
+		}));
 		fileByPath.set(effectivePath, page.sourceFile);
 		const composedLayout = page.layouts.length > 1 && layout !== void 0 ? composeLayoutLevel(page, layout) : void 0;
 		const stylesheetUrls = clientDir === void 0 ? [] : productionStylesheetUrls(clientDir, [

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 { 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"}
+{"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 — a shared mechanism now, not a promise: {@link layoutLevelOf} calls\r\n * `../routing/layout-level.ts`'s `resolveLayoutLevel`, the same selection and\r\n * prefix-composition rule dev's own `resolveLayoutLevel` calls, and\r\n * {@link composeLayoutLevel} folds loaders through the same\r\n * `./fold-layout-loaders.ts` dev's does — so the URL a page answers on and the\r\n * chain that guards it are decided by the page's own source in both modes, and\r\n * a build cannot quietly disagree with the dev server about 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 { duplicateRoutePathMessage } from \"../routing/duplicate-route-path\";\r\nimport { deriveFilesystemRoutePath } from \"../routing/filesystem-route\";\r\nimport { resolveLayoutLevel } from \"../routing/layout-level\";\r\nimport {\r\n  resolvePageRouteCache,\r\n  resolvePageRouteIdentity,\r\n  type PageCacheOptIn,\r\n} from \"../routing/route-identity\";\r\nimport { publishRouteTable } from \"../routing/route-table\";\r\nimport { 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 { foldLayoutLoaders } from \"./fold-layout-loaders\";\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} 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's own `LayoutModuleShape`.\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-error-transport.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 `install-page-routes.ts`'s\r\n * `filesystemPageFileFor`.\r\n */\r\nfunction webRelativeSourceFile(sourceFile: string): string {\r\n  return sourceFile.split(\"/\").slice(2).join(\"/\");\r\n}\r\n\r\n/**\r\n * Exported for `../routing/route-name-parity.spec.ts`, which proves this and\r\n * dev's own call agree — both now call the same `../routing/route-identity.ts`\r\n * `resolvePageRouteIdentity`, so this wrapper's only job is supplying THIS\r\n * installer's identifiers: the manifest `sourceFile` doubles as the\r\n * `route.path` rejection context, and its web-root-relative form is the\r\n * filesystem-derivation input.\r\n */\r\nexport function resolveRoute(\r\n  routeExport: PageRouteExport | undefined,\r\n  sourceFile: string,\r\n): { path: string; name: string } {\r\n  return resolvePageRouteIdentity(routeExport, webRelativeSourceFile(sourceFile), sourceFile);\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 its own `LayoutLevel.prefixesByDirectory`,\r\n * and the one {@link deriveFilesystemRoutePath} uses to let a directory's own\r\n * layout rename the URL segment a bare directory name would otherwise\r\n * 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 selection and prefix\r\n * rules themselves do not depend on where a layout's module came from, so\r\n * they live in one place both installers call —\r\n * `../routing/layout-level.ts`'s `resolveLayoutLevel` — rather than being\r\n * re-derived here against loaded modules instead of Vite's. This function's\r\n * own job is reading THIS installer's inputs off the manifest (`renders` and\r\n * `prefix` off each already-loaded module, `host` recovered from the shared\r\n * result's `hostId`) and nothing else.\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 (raised by the\r\n * shared `resolveLayoutLevel` itself). Like the missing app-root refusal\r\n * below, that defends against stale or hand-edited build artifacts: the build\r\n * refuses to emit such a chain, but a manifest can reach a running process\r\n * 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 level = resolveLayoutLevel(\r\n    page.sourceFile,\r\n    page.layouts.map((layout) => ({\r\n      id: layout.sourceFile,\r\n      renders: typeof (layout.module as LayoutModuleShape).default !== \"undefined\",\r\n      prefix: (layout.module as LayoutModuleShape).prefix,\r\n    })),\r\n  );\r\n\r\n  return {\r\n    host: page.layouts.find((layout) => layout.sourceFile === level.hostId),\r\n    prefix: level.prefix,\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: foldLayoutLoaders(\r\n      page.layouts.map((layout) => (layout.module as LayoutModuleShape).loader),\r\n      hostIndex,\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 in its\r\n    // own installer — so a malformed `cache` opt-in fails a production boot\r\n    // instead of shipping a page whose freshness window the framework\r\n    // 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 and discovery applies at build (`discover-pages.ts`), read\r\n    // here off the manifest's own `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        duplicateRoutePathMessage({\r\n          effectivePath,\r\n          existingFile,\r\n          newFile: page.sourceFile,\r\n          composition: { layoutPrefix, routePath },\r\n        }),\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":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAsIA,SAAS,sBAAsB,YAA4B;CACzD,OAAO,WAAW,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,GAAG;AAChD;;;;;;;;;AAUA,SAAgB,aACd,aACA,YACgC;CAChC,OAAO,yBAAyB,aAAa,sBAAsB,UAAU,GAAG,UAAU;AAC5F;;;;;;;;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;AAkDA,SAAS,cAAc,MAA0C;CAC/D,MAAM,QAAQ,mBACZ,KAAK,YACL,KAAK,QAAQ,KAAK,YAAY;EAC5B,IAAI,OAAO;EACX,SAAS,OAAQ,OAAO,OAA6B,YAAY;EACjE,QAAS,OAAO,OAA6B;CAC/C,EAAE,CACJ;CAEA,OAAO;EACL,MAAM,KAAK,QAAQ,MAAM,WAAW,OAAO,eAAe,MAAM,MAAM;EACtE,QAAQ,MAAM;CAChB;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,kBACN,KAAK,QAAQ,KAAK,WAAY,OAAO,OAA6B,MAAM,GACxE,SACF;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;EAMhE,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,0BAA0B;GACxB;GACA;GACA,SAAS,KAAK;GACd,aAAa;IAAE;IAAc;GAAU;EACzC,CAAC,CACH;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,7 +1,7 @@
 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 { FastifyInstance, Router } from "@warlock.js/core";
 import { ViteDevServer } from "vite";
 
 //#region ../web/src/server/install-page-routes.d.ts
@@ -39,7 +39,7 @@ type InstallPageRoutesOptions = {
   appSrcRoot: string; /** v5/app/src/web/root.tsx — the single global app-root file. */
   appFile: string;
   /**
-   * The application root Vite's dev server serves from — `dev-server.ts`'s
+   * The application root Vite's dev server serves from — `dev-error-transport.ts`'s
    * `paths.appRoot`, i.e. `<appRoot>/src === appSrcRoot` by default. Every
    * handler's stylesheet URLs are expressed relative to THIS, because that is
    * the root Vite's dev server actually resolves `/…` URLs against
@@ -64,6 +64,26 @@ type InstallPageRoutesOptions = {
    * page's own CSS" without also carrying every other page's.
    */
   stylesheetUrls?: readonly string[];
+  /**
+   * The Fastify instance `HttpConnector.boot()` published, resolved by the
+   * caller on the NODE side (`web-connector.ts`) and forwarded to every
+   * `createPageRouteHandler` call below instead of letting that factory read
+   * `container.get("http.server")` for itself.
+   *
+   * Load-bearing, not a convenience: Vite's SSR module runner
+   * (`vite.ssrLoadModule`, used throughout this file) evaluates
+   * `create-page-route-handler.ts` as a SECOND copy of `@warlock.js/core`, with
+   * its own `container` that `HttpConnector.boot()` never wrote to. Reading the
+   * container from inside that SSR graph therefore always misses, however
+   * early or late this file calls it — the value has to arrive as a plain
+   * argument from a caller on the Node side, where the real container lives.
+   *
+   * OPTIONAL so existing callers (and this file's own unit tests, which seed
+   * `container.set("http.server", …)` instead) keep resolving through the
+   * container exactly as before — omitted here means "not supplied", the same
+   * distinction `createPageRouteHandler` itself draws from `PageRouteHandlerOptions.httpServer`.
+   */
+  httpServer?: FastifyInstance;
 };
 /**
  * Registers every discoverable page into `options.router`. Throws

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

@@ -1,15 +1,18 @@
 import { publishRouteTable } from "../routing/route-table.mjs";
-import { isLoaderShortCircuit } from "./settle-page-response.mjs";
 import { composeRoutePath } from "../routing/compose-route-path.mjs";
+import { duplicateRoutePathMessage } from "../routing/duplicate-route-path.mjs";
+import { PageFileSegmentNotSupportedError } from "../routing/page-file-segment.mjs";
 import { deriveFilesystemRoutePath } from "../routing/filesystem-route.mjs";
-import { NestedLayoutsNotSupportedError, selectPageLayout } from "../routing/layout-policy.mjs";
-import { canonicalizeRouteExport, resolvePageRouteCache, resolvePageRouteName } from "../routing/route-identity.mjs";
+import { resolveLayoutLevel as resolveLayoutLevel$1 } from "../routing/layout-level.mjs";
+import { resolvePageRouteCache, resolvePageRouteIdentity, resolvePageRouteName } from "../routing/route-identity.mjs";
 import { createPageRouteHandler } from "./create-page-route-handler.mjs";
+import { foldLayoutLoaders } from "./fold-layout-loaders.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";
 import { NonLiteralRouteExportError, readRouteExports } from "../build/read-route-exports.mjs";
-import { ErrorPageDeclaresRouteError, discoverPageFiles, isErrorPageFile, layoutChainFor, toPosix } from "../build/discover-pages.mjs";
-import { Response } from "@warlock.js/core";
+import { toPosix } from "../shared/to-posix.mjs";
+import { ErrorPageDeclaresRouteError, discoverPageFiles, isErrorPageFile, layoutChainFor } from "../build/discover-pages.mjs";
+import "@warlock.js/core";
 import path from "node:path";
 
 //#region ../web/src/server/install-page-routes.ts
@@ -20,10 +23,10 @@ import path from "node:path";
 * the sanctioned dev-server dispatch path (server matching is Warlock's
 * router; there is no second server matcher) — picks
 * it up. Replaces the two hand-rolled `fastify.get()` calls this file's
-* sibling, `dev-server.ts`, used to make directly.
+* sibling, `dev-error-transport.ts`, used to make directly.
 *
 * DELIBERATE EXCEPTION to "web has no core dependency", same
-* reasoning `dev-server.ts`'s own header comment records: this module is not
+* reasoning `dev-error-transport.ts`'s own header comment records: this module is not
 * exported from either package barrel and is not part of `web/package.json`'s
 * dependency graph — dev/CLI bootstrap only.
 *
@@ -63,34 +66,82 @@ function filesystemPageFileFor(pageFile, appSrcRoot) {
 	return toPosix(path.relative(path.join(appSrcRoot, "web"), pageFile));
 }
 /**
-* Resolve the stable identity used to distinguish a route-export edit from an
-* ordinary component-body edit. The declared path is retained before layout
-* composition so `/settings` under `/admin` compares with the next declared
-* `/settings`, not with the effective `/admin/settings` route.
+* Raised when a page's own module fails to load in dev (`vite.ssrLoadModule`
+* rejects on the page file itself — never a layout, which this class does not
+* cover).
+*
+* Before this class existed, that rejection propagated straight out of
+* `installPageRoutes`'s loop and failed the WHOLE install: every other page's
+* route went unregistered along with the broken one, and the failure named
+* neither the page file nor which module actually threw. One bad page taking
+* every other page down with it is a worse outage than the bad page alone, so
+* this error is what the broken page's own route now fails with instead —
+* named, with its cause attached, while the rest of the application keeps
+* serving.
 */
-function resolvePageRouteIdentity(routeExport, pageFile, appSrcRoot) {
+var PageModuleLoadError = class extends Error {
+	pageFile;
+	constructor(pageFile, cause) {
+		const rawCause = cause instanceof Error ? cause.message : String(cause);
+		const causeMessage = /[.!?]$/.test(rawCause.trim()) ? rawCause.trim() : `${rawCause.trim()}.`;
+		super(`"${pageFile}" failed to load: ${causeMessage} Every other page still installed and is still serving; fix the error in this page's module and it will start serving again.`, { cause });
+		this.pageFile = pageFile;
+		this.name = "PageModuleLoadError";
+	}
+};
+/**
+* Registers a page whose OWN module failed to load at its filesystem-derived
+* URL, so a request there reports {@link PageModuleLoadError} — naming the
+* page file and the underlying cause — instead of a bare 404 that explains
+* nothing.
+*
+* Only the filesystem-derived path is attempted: the page's `route` export
+* cannot be read (that requires the very module that failed to load), and its
+* layout chain is not resolved either, so no layout prefix composes into this
+* path. When the filesystem path itself is not derivable
+* (`deriveFilesystemRoutePath` rejects a segment), there is no path left to
+* register a route at, so nothing is registered — the caller reports both
+* failures loudly at boot and moves on.
+*/
+async function registerFailedPageRoute(input) {
+	const { router, pageFile, appSrcRoot, loadError, fileByPath } = input;
+	const attributed = new PageModuleLoadError(pageFile, loadError);
 	const filesystemPageFile = filesystemPageFileFor(pageFile, appSrcRoot);
-	if (routeExport === void 0) return {
-		declaredPath: deriveFilesystemRoutePath({ pageFile: filesystemPageFile }),
-		name: resolvePageRouteName(routeExport, filesystemPageFile)
-	};
-	return {
-		declaredPath: canonicalizeRouteExport(routeExport, pageFile).path,
-		name: resolvePageRouteName(routeExport, filesystemPageFile)
-	};
+	let effectivePath;
+	try {
+		effectivePath = deriveFilesystemRoutePath({ pageFile: filesystemPageFile });
+	} catch (segmentError) {
+		if (!(segmentError instanceof PageFileSegmentNotSupportedError)) throw segmentError;
+		console.error(attributed.message);
+		console.error(segmentError.message);
+		return;
+	}
+	const existingFile = fileByPath.get(effectivePath);
+	if (existingFile) throw new Error(duplicateRoutePathMessage({
+		effectivePath,
+		existingFile,
+		newFile: pageFile
+	}));
+	fileByPath.set(effectivePath, pageFile);
+	await router.withSourceFile(canonicalSourceFileFor(pageFile, appSrcRoot), () => router.get(effectivePath, async () => {
+		throw attributed;
+	}, {
+		name: resolvePageRouteName(void 0, filesystemPageFile),
+		isPage: true
+	}));
 }
 async function resolveLayoutLevel(pageFile, webRoot, loadLayout) {
 	const chain = layoutChainFor(pageFile, webRoot);
 	const modules = await Promise.all(chain.map(loadLayout));
-	const selection = selectPageLayout(chain.map((layout, index) => ({
-		layout,
-		renders: typeof modules[index].default !== "undefined"
+	const level = resolveLayoutLevel$1(pageFile, chain.map((layoutFile, index) => ({
+		id: layoutFile,
+		renders: typeof modules[index].default !== "undefined",
+		prefix: modules[index].prefix
 	})));
-	if (selection.type === "rejected") throw new NestedLayoutsNotSupportedError(pageFile, selection.layouts);
 	return {
 		chain,
-		layoutFile: selection.type === "selected" ? selection.layout : chain.at(-1),
-		prefix: modules.reduce((composed, layoutModule) => composeRoutePath(composed, layoutModule.prefix ?? "/"), "/"),
+		layoutFile: level.hostId,
+		prefix: level.prefix,
 		prefixesByDirectory: Object.fromEntries(chain.flatMap((layoutFile, index) => {
 			const prefix = modules[index].prefix;
 			return prefix === void 0 ? [] : [[toPosix(path.relative(webRoot, path.dirname(layoutFile))), prefix]];
@@ -113,15 +164,7 @@ async function composeLayoutLevel(level, loadLayout) {
 	return {
 		...modules[hostIndex],
 		middleware: modules.flatMap((layoutModule) => [...layoutModule.middleware ?? []]),
-		loader: async (context) => {
-			let hostData;
-			for (let index = 0; index < modules.length; index++) {
-				const value = await modules[index].loader?.(context);
-				if (value instanceof Response || isLoaderShortCircuit(value)) return value;
-				if (index === hostIndex) hostData = value;
-			}
-			return hostData;
-		}
+		loader: foldLayoutLoaders(modules.map((layoutModule) => layoutModule.loader), hostIndex)
 	};
 }
 /**
@@ -134,7 +177,8 @@ async function composeLayoutLevel(level, loadLayout) {
 * below `src/web`, using the same pure filesystem-routing helper as the build.
 */
 async function installPageRoutes(options) {
-	const { router, vite, appSrcRoot, appFile, hydrationClientModuleUrl } = options;
+	const { router, vite, appSrcRoot, appFile, hydrationClientModuleUrl, httpServer } = options;
+	const httpServerOption = httpServer === void 0 ? {} : { httpServer };
 	const stylesheetRoot = options.appRoot ?? path.dirname(appSrcRoot);
 	const discovered = [...discoverPageFiles(appSrcRoot)].sort((left, right) => left.pageFile < right.pageFile ? -1 : left.pageFile > right.pageFile ? 1 : 0);
 	const errorPageFiles = discovered.filter((page) => isErrorPageFile(page.pageFile));
@@ -152,9 +196,21 @@ async function installPageRoutes(options) {
 	const installed = [];
 	const fileByPath = /* @__PURE__ */ new Map();
 	for (const { pageFile, webRoot } of pageFiles) {
-		const pageModule = await vite.ssrLoadModule(pageFile);
+		let pageModule;
+		try {
+			pageModule = await vite.ssrLoadModule(pageFile);
+		} catch (loadError) {
+			await registerFailedPageRoute({
+				router,
+				pageFile,
+				appSrcRoot,
+				loadError,
+				fileByPath
+			});
+			continue;
+		}
 		const sourceFile = canonicalSourceFileFor(pageFile, appSrcRoot);
-		const { declaredPath: routePath, name } = resolvePageRouteIdentity(pageModule.route, pageFile, appSrcRoot);
+		const { path: routePath, name } = resolvePageRouteIdentity(pageModule.route, filesystemPageFileFor(pageFile, appSrcRoot), pageFile);
 		const cache = resolvePageRouteCache(pageModule.route, pageFile);
 		const loadLayout = (layoutFile) => vite.ssrLoadModule(layoutFile);
 		const layoutLevel = await resolveLayoutLevel(pageFile, webRoot, loadLayout);
@@ -164,7 +220,15 @@ async function installPageRoutes(options) {
 			layoutPrefixes: layoutLevel.prefixesByDirectory
 		}) : composeRoutePath(layoutPrefix, routePath);
 		const existingFile = fileByPath.get(effectivePath);
-		if (existingFile) throw new Error(`installPageRoutes: composed route path "${effectivePath}" (layout prefix "${layoutPrefix}" + route.path "${routePath}") is declared by two pages (web/src/server/install-page-routes.ts) — "${existingFile}" and "${pageFile}". Every page's composed route path must be unique.`);
+		if (existingFile) throw new Error(duplicateRoutePathMessage({
+			effectivePath,
+			existingFile,
+			newFile: pageFile,
+			composition: {
+				layoutPrefix,
+				routePath
+			}
+		}));
 		fileByPath.set(effectivePath, pageFile);
 		const stylesheetUrls = devHandlerStylesheetUrls(stylesheetRoot, [
 			appFile,
@@ -185,7 +249,8 @@ async function installPageRoutes(options) {
 			hydrationClientModuleUrl,
 			loadErrorPage,
 			stylesheetUrls,
-			cache
+			cache,
+			...httpServerOption
 		}), {
 			name,
 			isPage: true
@@ -215,7 +280,8 @@ async function installPageRoutes(options) {
 			stylesheetUrls: devHandlerStylesheetUrls(stylesheetRoot, [appFile, notFoundPageFile]),
 			matchPath: (requestPath) => requestPath,
 			statusForRenderedOk: 404,
-			skipPageLoader: true
+			skipPageLoader: true,
+			...httpServerOption
 		}) }), {
 			name: NOT_FOUND_ROUTE_NAME,
 			isPage: true
@@ -228,5 +294,5 @@ async function installPageRoutes(options) {
 }
 
 //#endregion
-export { installPageRoutes, resolvePageRouteIdentity };
+export { filesystemPageFileFor, installPageRoutes };
 //# sourceMappingURL=install-page-routes.mjs.map