@teamscala/service-boot 0.23.522 → 0.23.524

package/src/orpc-openapi-gate.ts

@@ -1,18 +1,6 @@
 /**
  * @system service-boot
- * @status handwritten — none derivable: the gate is a REJECTION RULE over four request facts, and no row states a rule — searched the service-boot auth surfaces (auth-gate.ts, auth/, content-gate/, gpt-gate.ts, bind-page-handler.ts) for an existing static-key check to call, and public-paths.ts names exempted PATHS, never a verifier
- * @edit edit directly
- *
- * THE OpenAPI CONTRACT GATE: who may read the document.
- *
- * It refuses a PROXIED request even when the key is right. The guard
- * `auth-helpers-fail-closed` holds a static key internal-only and never a
- * public sole-gate, and names the remedy: also reject on proxy-header
- * presence. Here the two are one fact from both sides — public ingress
- * crosses the tunnel and injects those headers, an internal fetch carries
- * neither, and the MCP gateway is the internal fetch.
- *
- * EVERY REFUSAL IS A REFUSAL: no key, no header, wrong key, proxied.
+ * @status handwritten
  */
 
 /**

package/src/page-route-shell-types.ts

@@ -1,13 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Render mode literal shared across page route registration. The old
- * shell-variant types (LegacyShell, PageSlugShell, RegionsShell,
- * PublicShell, ConfigPageRoute) were removed when the Phase 2 deploy-time
- * `service_install.page_routes[]` path was eliminated — all routing is
- * now registry-driven `page_route` rows (Phase 1).
  */
 
 export type RenderModeLiteral =

package/src/page-server-loader-graph.ts

@@ -1,16 +1,6 @@
 /**
  * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * page-server-loader-graph.ts — binds the ONE loader-graph resolver
- * (@teamscala/resolver-engine's createLoaderConfigResolver) to the page-server
- * SSR client. The resolver used to be duplicated here with its own algorithm;
- * the copies drifted (a non-UUID URL ref resolved absent on this surface and
- * still threw into the render breaker on the fn-router surface), so the
- * algorithm became one injected function and each surface binds its own
- * client source. This module IS that binding for the SSR surface — the single
- * place the page-server client and the loader-graph resolver meet.
  */
 
 import { createLoaderConfigResolver } from "@teamscala/resolver-engine/loader-config/resolve-from-loader-config";

package/src/page-server-orpc/hub-mcp-client.ts

@@ -1,12 +1,6 @@
 /**
- * @system page-server
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Module-level singleton for the hub MCP client. setHubMcpClient(client)
- * is called once at boot by the host service after creating the multi-
- * tenant MCP client; createPageHandler's resolve-page-state reads it via
- * getHubMcpClient to pass through to data loaders.
  */
 
 let _hubMcpClient: unknown | null = null;

package/src/page-server-orpc/server-client.ts

@@ -1,28 +1,6 @@
 /**
- * @system page-server
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Server-side ORPC client for in-process direct invocation, per the canonical
- * Vite/Next/Nuxt SSR pattern documented at https://orpc.dev/docs/best-practices/optimize-ssr
- *
- * The host service (scala-install) must call `setServerClient(client)` once
- * at boot, after createRouterClient(appRouter, { context: { prisma } }).
- * Then page-server's createPageHandler reads `getServerClient()` per request
- * — no HTTP loopback, just a typed function call.
- *
- * NO EMPTY-ROUTER SUBSTITUTE. This used to answer an unregistered read by
- * fabricating `createRouterClient({}, …)` — a client with no models on it. That
- * turned "boot never registered a client" into "every model lookup returns
- * undefined", which surfaces far away as MissingLoaderModelCapabilityError on
- * page render rather than as a boot failure. Measured 2026-08-20: quiz and forms
- * served 500s on every data-backed page for hours while /health returned 200 and
- * boot logged "ORPC serverClient registered", because the empty router is
- * indistinguishable from a real one until something asks it for a model
- * (`a-component-may-not-report-a-state-it-has-not-verified`).
- *
- * A missing client is now a thrown error naming the boot step that should have
- * set it, so the failure is reported by the component that has the fault.
  */
 
 import { createRouterClient } from "@orpc/server";

package/src/pg-boss-handler-registry.ts

@@ -1,17 +1,6 @@
 /**
- * @system server-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * The pg-boss scheduled-job handler registry — `handler_slug` → handler
- * function. Built on `@teamscala/generic-registry` `createRegistry` (the mandated
- * primitive per `generic-registry-is-the-only-registry-pattern`); a hand-rolled
- * Map or a hardcoded switch in service-boot is the prohibited alternative.
- *
- * Handlers live in packages and self-register at boot (a boot hook / package
- * subscriber shape) by calling `registerScheduledJobHandler`. `resolveHandler`
- * in `pg-boss-mount.ts` reads this registry to dispatch a firing `scheduled_job`
- * row to its registered function.
  */
 import type { ScheduledJobConfig } from "@teamscala/db-validation/registry-schemas/scheduled-job";
 import { createRegistry } from "@teamscala/generic-registry/create-registry";

package/src/pg-boss-mount.ts

@@ -1,13 +1,6 @@
 /**
- * @system server-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Mounts pg-boss for a backend service. Reads all scheduled_job registry
- * entries scoped to the current service from the registry cache, registers
- * pg-boss workers per queue_name, and schedules cron/interval jobs.
- * Per Constitution Rule 6: pg-boss is the single mechanism for all
- * application background work.
  */
 
 import type { ScheduledJobConfig } from "@teamscala/db-validation/registry-schemas/scheduled-job";

package/src/proposal-authorized-emails.ts

@@ -1,38 +1,6 @@
 /**
  * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Resolves the set of emails authorized to view a proposal. A proposal is
- * gated (proposal-access) — only these emails can unlock it:
- *
- *   - the issuing-org team: every member of the proposal's organisation
- *     (better_auth_member → user.email). Lets the agency team open any of their
- *     own proposals AND covers existing proposals whose created_by is
- *     "system"/null.
- *   - the recipient: the proposal's CRM contact (client_database.primary_email),
- *     when contact_id is set.
- *   - the partner team: every CRM contact belonging to the proposal's partner
- *     org (client_database.company_id = proposals.partner_id → primary_email),
- *     when partner_id is set. Lets the co-delivery partner's team open a
- *     co-branded proposal. The partner is still branding-first; this is the one
- *     access edge it carries.
- *
- * The partner clause casts to ::uuid because the two sides disagree in the
- * database: client_database.company_id is `uuid` while proposals.partner_id is
- * `text`. Postgres resolves operators at PLAN time, so `uuid = text` raises
- * "operator does not exist" for EVERY proposal — including ones with no partner
- * — the catch below swallows it, and the fail-closed empty Set then denies
- * access to everyone. Measured 2026-09-10: no proposal could be unlocked by any
- * email. The cast is correct once partner_id becomes `uuid` too (a no-op then);
- * the column type is the real fix and is tracked separately.
- *
- * Uses $queryRaw (raw SQL) deliberately: the per-service Prisma client is scoped
- * to that service's own models, so the proposals service's client has no
- * `member`/`user` model methods — but $queryRaw runs against the shared DB
- * regardless of the client's model scope. Returns a lowercased Set, checked
- * server-side only (emails never sent to the client). Fail-closed: any error
- * yields an empty set (no access).
  */
 
 import { getAppLogger } from "@teamscala/logger/app-loggers";

package/src/proposal-gate.ts

@@ -1,17 +1,6 @@
 /**
  * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * The PROPOSAL content gate, expressed as config for the content-gate primitive
- * (content-gate/). No bespoke gate plumbing — just the proposal-specific bits:
- * which resource (resolved.proposal.id), who's authorized (issuing-org team +
- * recipient), what to seed (initialVisitor for the chat), and how to withhold
- * (replace the proposal body with an injected SignIn gate block + neutralize the
- * meta tags). The engine handles cookie/token/verify/orchestration.
- *
- * Universal: every proposal route exposes resolved.proposal, so this gates every
- * proposal (existing + new) with no per-page block or migration.
  */
 
 import type { AccessConfig, ContentGateConfig } from "./content-gate/config-types.ts";

package/src/quiz-gate.ts

@@ -1,28 +1,6 @@
 /**
  * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * The PUBLIC QUIZ identity gate, expressed as config for the content-gate
- * primitive. Like the GPT gate this is lead capture, not access control: every
- * email is a valid visitor. Its job is to make the visitor KNOWN AT SSR so the
- * page's identity blocks hide themselves and the quiz blocks reveal themselves
- * — by block condition on `initialVisitor`, never by a component deciding which
- * screen to render.
- *
- * That is the whole point of this file existing. The quiz identity form used to
- * be a composite React component that hand-assembled a logo, a heading, three
- * inputs and a button, and then branched in TypeScript on whether a visitor was
- * known. Every one of those pieces is already a Puck block, and the branch is
- * already expressible as a block condition — what was missing was only the
- * server half: something to turn a submitted email into a visitor the next
- * render can see. This is that half, and it is 60 lines of config because the
- * engine (content-gate/gate.ts + access.ts) already does the work.
- *
- * Flow: the composed form POSTs {quizId, name, email, phone} to
- * /api/quiz-access (openCapture → any email matches); the access endpoint signs
- * a `quiz_token` cookie and redirects back. On the next request runContentGate
- * verifies it for this assessment and seeds resolved.initialVisitor.
  */
 
 import type { AccessConfig, ContentGateConfig } from "./content-gate/config-types.ts";

package/src/read-html-template.ts

@@ -1,54 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Builds the shared React/Puck document envelope and substitutes the current
- * content-hashed asset URLs from `dist/client/asset-manifest.json`.
- *
- * The envelope is runtime-owned. UI services are Puck compositions and must
- * not carry or generate a per-service `src/index.html`; requiring that file
- * creates a second rendering surface that can disappear independently of the
- * Hono + React/Puck runtime.
- *
- * Build-time produces hashed filenames (e.g. `styles-abc123.css`); the
- * static-asset handler serves them with `cache-control: immutable`. New
- * deployments emit new hashes → new URLs → browsers refetch without ever
- * holding a stale copy. Without the substitution, a fixed
- * `/assets/styles.css` paired with `immutable` would pin every visitor to
- * whatever version they first downloaded.
- *
- * Cached per service process, keyed on the manifest's mtime. The cache MUST
- * invalidate when `asset-manifest.json` changes: `buildClientAssets` can
- * rebuild the bundle AFTER the first request — producing a new content hash,
- * rewriting the manifest, AND deleting the old hashed bundle
- * (`removeStaleHashedFiles`). A lifetime-pinned HTML cache then keeps serving
- * the OLD hash, which now 404s → hydration never runs → the page renders SSR
- * HTML but is dead client-side (the doc-editor overlay never mounts; scala-docs
- * 2026-06-13, exposed by the ui-foundation publish-storm's repeated rebuilds).
- * Re-stat'ing the tiny manifest per request is negligible (OS-cached, no
- * network); the substituted HTML is reused while the mtime is unchanged.
- *
- * NO SERVED HTML WITHOUT A VERIFIED MANIFEST: when the manifest is absent,
- * unreadable, or names files that do not exist, this module THROWS rather
- * than emitting HTML — the fixed-name fallback (`/assets/styles.css`,
- * `/assets/hydrate.js`) it once served names files NOTHING builds, so a
- * 200 page with those URLs was a stylesheet 404 wearing a working page's
- * clothes. Measured 2026-09-01: proposals.scala.business served a
- * client-facing proposal unstyled while Railway reported the deploy
- * SUCCESS. The readiness flip now gates on `verifyClientBuildAssets`
- * (build-client-assets/manifest.ts), so this throw is defence in depth for
- * a manifest that vanishes mid-process; the page-server render catch turns
- * it into the branded error page, never a 200 with dead URLs.
- *
- * NO-SILENT-REVERTS: when the manifest is a TOMBSTONE (the last client build
- * failed), the served HTML is stamped with a `<meta name="x-client-build-status"
- * content="failed">` tag in <head> so any operator / chrome-devtools / theme
- * probe inspecting the page can see the served bundle is STALE (a published fix
- * that reached node_modules but failed to bundle is silently served from the
- * prior bundle otherwise — scala-agents 2026-07-18, the white-on-white toolbar
- * regression that looked "not fixed" while the bundle kept serving pre-fix
- * bytes across restarts).
  */
 
 import { createCache } from "@teamscala/cache/create-cache";

package/src/readiness-gate.ts

@@ -1,14 +1,6 @@
 /**
  * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Readiness gate — returns 503 + Retry-After: 1 until the boot pipeline
- * flips the ready flag true as its last step. Registered as the FIRST
- * middleware in both UI and backend boot paths per readiness-gated-boot.
- *
- * The gate fails open: if it ever throws, the request passes through to
- * the normal handler rather than producing a hard 500.
  */
 
 import { getAppLogger } from "@teamscala/logger/app-loggers";

package/src/register-api-routes.ts

@@ -1,16 +1,6 @@
 /**
- * @system server-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Walks `service_install.api_routes[]` and binds each entry to its
- * registered handler (via mountRegistry.handlers, populated by server_packages
- * during their mount phase). Unresolved handler_slug values are fatal — the
- * service cannot boot with declared routes pointing at nothing.
- *
- * Injects x-remote-port header from Bun's getConnInfo so downstream
- * handlers (MCP route) can resolve caller identity via process-tree
- * walking when explicit caller headers are absent.
  */
 
 import type { ServiceInstallConfig } from "./load-service-install-row";

package/src/register-crash-handlers.ts

@@ -1,11 +1,6 @@
 /**
- * @system server-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Registers process-level crash handlers (unhandledRejection, uncaughtException)
- * for a given service. Each handler logs the error with the service slug for
- * identification. Per constitution crash-isolation.
  */
 
 import { getAppLogger } from "@teamscala/logger/app-loggers";

package/src/register-page-routes.ts

@@ -1,17 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit directly
- *
- * Page route registration — reads `page_route` registry rows for the
- * current service and delegates to `registerRegistryPageRoute`.
- *
- * All routes are registry-driven (Phase 1): each `page_route` row pairs
- * a URL pattern with a `resource_loader` graph that resolves data in
- * wave-parallel via `resolveFromLoaderConfig`. No deploy-time shell
- * variant routes — the old `service_install.page_routes[]` Phase 2 path
- * was removed when every active service migrated to registry-driven
- * `page_route` rows (all 9 services carry empty arrays).
  */
 
 import { BootFatalError } from "@teamscala/os/errors/boot-error";

package/src/register-page-server-client.ts

@@ -1,18 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Registers the system server-client for page-server SSR rendering. Composes
- * the platform-owned routers into the service's generated `appRouter` and
- * stashes the resulting client via setServerClient. Called once at boot before
- * any page route handler fires.
- *
- * Handwritten because no machine-readable contract generates it: this is the
- * EXECUTOR half of a rows+executor pair (`business-logic-is-rows-plus-executors`),
- * whose declared half is the `service_install`/`service_schema` rows read at
- * boot. There is no supplier spec, CLI or registry row that could emit this
- * boot-time wiring, so it stays hand-written; the row half remains the source.
  */
 
 		// REFUSE, DO NOT SKIP. `existsSync(routerPath)` being false used to fall straight through with appRouter=null and still register a client + log

package/src/register-registry-page-route/ai-chat-prefetch.ts

@@ -1,11 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * SSR-prefetch the signed-in user's AI-chat conversation so a click-opened AI
- * panel renders the real conversation on first paint. Extracted from
- * register-registry-page-route.ts (single-purpose-file split).
  */
 /**
  * SSR-prefetch the signed-in user's AI-chat conversation so a CLICK-opened AI

package/src/register-registry-page-route/apply-page-branding.ts

@@ -1,15 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * The three brand-override paths of a registered page route: the /sign-in
- * callback-org override, the signed-in session-org personalisation
- * (platform pages only), and the brand_org_path resource-owner override.
- *
- * Split out of register-registry-page-route.ts (924 lines) — the loadData
- * closure segments moved byte-identical; only the closure variables became
- * explicit parameters.
  */
 
 /**

package/src/register-registry-page-route/captured-loader-config.ts

@@ -1,16 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Summarises the resource_loader config a route captured at boot, for the
- * route-registration log line. Registration reads the loader row ONCE into
- * the route closure, so an edit to the row silently does not reach the
- * running service (measured 2026-08-18: a footer region added to a report
- * produced no footer and no diagnostic until a cold wake). Naming the
- * captured shape in the boot log makes the row-vs-running-service gap a
- * one-glance check in the service logs, and the restart contract is stated
- * where the operator will be looking when the edit "doesn't work".
  */
 
 /** Structural slice of the ResourceLoaderConfigSchema output this unit reads. */

package/src/register-registry-page-route/graph-cache.ts

@@ -1,26 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * The two SWR loader-graph caches (static-shell + parameterised routes) for the
- * registry page registrar, plus readCachedGraph — the testable stale-while-
- * revalidate read. Extracted from register-registry-page-route.ts so the SWR
- * decision is unit-testable independent of the Hono/DB/graph machinery.
- *
- * The SWR contract rides @teamscala/cache directly (the hand-rolled `at` timestamp,
- * FRESH_MS window, and graphRefreshInflight single-flight Set are gone): each
- * cache is configured ttlMs = the fresh window (serve, no refresh) + staleTtlMs =
- * the rest (serve stale + fire ONE background refresh). readCachedGraph uses
- * getWithMeta for the fresh/stale/miss decision and cache.refreshInBackground
- * for the fire-and-forget refresh — deduped against the cache's own in-flight map
- * (so delete/clear/disable drop its flights, and a refresh in flight across an
- * invalidation can no longer resurrect the dropped entry).
- *
- * Graphs deep-clone on BOTH set and get at the caller (registerRegistryPageRoute):
- * gateAgreementContent + downstream block resolution MUTATE the object in place,
- * so handing a cached tree out twice would ship request A's resolved data to
- * request B (ssr-first-tick-parity). Clone-on-get stays local to the caller.
  */
 /**
  * Stale-while-revalidate read of a cached loader graph.

package/src/register-registry-page-route/live-loader-config.ts

@@ -1,27 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * live-loader-config.ts — the per-request resource_loader read.
- *
- * The constitution's deploy-time bake list (installer-and-runtime) names
- * service_install, service_manifest, block_schema, page_route, api_route and
- * scheduled_job — resource_loader is NOT among it, so a loader row is runtime
- * data: a registry edit must reach the running service on a subsequent request
- * without a restart. This module is that contract: `readLiveLoaderConfig`
- * re-reads the row through `loadRegistryConfig` on EVERY request (its SWR
- * cache makes the fresh-window hit a memory read, not a DB round trip) and
- * FAILS CLOSED — a row that vanished or stopped validating mid-flight throws
- * into the branded error path rather than silently serving the boot-time
- * snapshot of a row that no longer exists.
- *
- * `fingerprintLoaderConfig` gives the per-request graph cache a key component
- * derived from the LIVE config, so a row edit invalidates cached graphs for
- * that route immediately (the graph cache keys on route+host+path alone would
- * otherwise serve a stale graph until its SWR window lapsed — right cache,
- * wrong key: the graph is a function of the config, so the config belongs in
- * the key).
  */
 
 import { loadRegistryConfig } from "@teamscala/db/registry/load-config";

package/src/register-registry-page-route/meta-title.ts

@@ -1,17 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Meta/title helpers for the route registrar: interpolate the route's
- * meta_context against the resolved graph. Extracted from
- * register-registry-page-route.ts.
- *
- * resolveTemplateTitle (the page_meta_template title reader) was DELETED
- * 2026-08-17: it only ever applied when NO resource entity resolved, and on a
- * resource page an entity ALWAYS resolves — the curated template was discarded
- * by construction, dead on exactly the pages the type exists for (Valencia's
- * finding). composePageTitle (+ the org-prefix flag) owns titles end to end.
  */
 /**
  * THE ONE SUBJECT DERIVATION. What a page is ABOUT — the entity whose name the

package/src/register-registry-page-route/page-data-shared.ts

@@ -1,17 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Shared Puck-page-data helpers for the resolved-graph → pageData conversion:
- * the PuckData alias of the canonical boundary Data, JSON extraction with an
- * honest null on
- * malformed input, layout-default application, region root-prop picking, the
- * RegionEntry shape, and the unresolved-region-slot warn. Plus the brand-token
- * prologue shared by all three render branches.
- *
- * Split out of resolve-page-data.ts (547 lines) — byte-for-byte moves; only
- * closure variables became explicit parameters.
  */
 
 import { getAppLogger } from "@teamscala/logger/app-loggers";

package/src/register-registry-page-route/prefetch-org-id.ts

@@ -1,12 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Resolves the organisation id for the background AI-chat session prefetch
- * from the request path. A canonical portal URL is /<websiteId>/<orgId>/
- * <path> — the org is segment 1, NOT segment 0. Moved from
- * register-registry-page-route.ts.
  */
 
 /**

package/src/register-registry-page-route/proposal-approval-email-token.ts

@@ -1,16 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Resolve the `{{approvalEmail}}` token on a proposal page, after pageData is
- * built.
- *
- * Split from proposal-post-processors.ts, which single-purpose-file correctly
- * flagged as two unrelated export groups. This unit is an async ORPC lookup
- * that rewrites button props; its former co-tenants are synchronous brand
- * stamping that touch no network. Sharing a file made an I/O-bound resolver
- * look like a pure formatter.
  */
 /**
  * Resolve the `{{approvalEmail}}` placeholder in a proposal page's button props

package/src/register-registry-page-route/proposal-brand-stamping.ts

@@ -1,16 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Stamp partner and client brand assets onto a proposal page's pageData, after
- * it is built.
- * Split from proposal-post-processors.ts (single-purpose-file: two unrelated
- * export groups). Both helpers here are synchronous, take an already-resolved
- * loader-graph org, and only map a logo/colour onto pageData — no network, no
- * ORPC. The approval-email token resolver they used to share a file with is an
- * async ORPC lookup, which is the distinction that was invisible while they sat
- * together.
  */
 
 /**

package/src/register-registry-page-route/public-shell-page-data.ts

@@ -1,13 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Branch 2 of the resolved-graph → pageData conversion: the public shell
- * (header/body/footer regions from header/footer sources).
- *
- * Split out of resolve-page-data.ts (547 lines) — byte-identical body; only
- * the closure variables became explicit parameters.
  */
 
 import { resolveThemeMode } from "../resolve-theme-mode.ts";

package/src/register-registry-page-route/region-slots-page-data.ts

@@ -1,13 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Branch 1 of the resolved-graph → pageData conversion: arbitrary region-slots
- * (portal/agents/docs) driven by resource_loader.region_slots.
- *
- * Split out of resolve-page-data.ts (547 lines) — byte-identical body; only
- * the closure variables became explicit parameters.
  */
 
 import { resolveThemeMode } from "../resolve-theme-mode.ts";

package/src/register-registry-page-route/resolve-page-data.ts

@@ -1,15 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * Converts the resolved loader-graph into the pageData shape the renderer
- * consumes — three branches: arbitrary region-slots (portal/utility), the
- * header/body/footer public shell, and the single-page fallback. Extracted
- * from register-registry-page-route.ts (single-purpose-file split); the three
- * branches + shared helpers were split out of THIS file at 547 lines
- * (region-slots-page-data.ts, public-shell-page-data.ts, single-page-data.ts,
- * page-data-shared.ts).
  */
 
 import { regionSlotsPageData } from "./region-slots-page-data.ts";

package/src/register-registry-page-route/resolve-panel-page.ts

@@ -1,15 +1,6 @@
 /**
- * @system ui-service-boot
+ * @system service-boot
  * @status handwritten
- * @edit edit directly
- *
- * ?panel=<slug> resolution: reads the panel_view row, follows its
- * content.page_slug to the builda_pages row, and stashes the panel page
- * data + active panel slug on pageData.
- *
- * Split out of register-registry-page-route.ts (924 lines) — the loadData
- * closure segment moved byte-identical; only the closure variables became
- * explicit parameters.
  */
 
 import { getServerClient } from "../page-server-orpc/server-client.ts";