@uniweb/runtime 0.17.2 → 0.18.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/runtime",
-  "version": "0.17.2",
+  "version": "0.18.1",
   "description": "Minimal runtime for loading Uniweb foundations",
   "type": "module",
   "exports": {
@@ -36,7 +36,7 @@
     "node": ">=20.19"
   },
   "dependencies": {
-    "@uniweb/core": "^0.23.0",
+    "@uniweb/core": "^0.24.0",
     "@uniweb/theming": "^0.1.15"
   },
   "devDependencies": {
@@ -44,7 +44,7 @@
     "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0",
     "vite": "^7.3.1",
     "vitest": "^4.1.7",
-    "@uniweb/build": "0.41.0"
+    "@uniweb/build": "0.42.0"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/appearance.js

@@ -28,7 +28,7 @@
  *
  * Environment-neutral by construction. `applyBootScheme` no-ops its DOM writes
  * outside a browser, and `renderAppearanceBootScript` only stringifies — so
- * ssr-renderer.js can import this module in Node and in a Cloudflare isolate.
+ * ssr-renderer.js can import this module in Node and in a server-side isolate.
  *
  * Two writers with independent resolution is the bug this replaced:
  * WebsiteRenderer used to re-apply `appearance.default` from an effect, and

package/src/collect-records.js

@@ -78,7 +78,7 @@ import { createDefaultFetcher } from './default-fetcher.js'
  */
 export async function collectSiteRecords(
   content,
-  { locale, fetch, signal, only = null, depth = 'brief', maxPages } = {},
+  { locale, fetch, signal, only = null, whole = false, maxPages } = {},
 ) {
   const config = content?.config
   const services = config?.services ?? null
@@ -111,7 +111,7 @@ export async function collectSiteRecords(
     if (!cfg.ask) return
     // `limit` is the list page's, never the corpus's — see the header.
     const { limit, ...population } = cfg
-    const asked = { ...population, depth, exhaustive: true }
+    const asked = { ...population, whole, exhaustive: true }
     if (typeof maxPages === 'number' && maxPages > 0) asked.maxPages = maxPages
 
     const result = await fetcher.resolve(asked, { signal })

package/src/default-fetcher.js

@@ -230,12 +230,13 @@ export function createDefaultFetcher({ basePath = '', dev = false, fetch: fetchI
         // it returned.
         data = applyOperators(data, request, { dev })
 
-        // ⭐ Say what depth was delivered, so the record index can file it — what
-        // the config asked for, echoed: a list at brief depth when the query has
-        // a per-record source, a record in full. (The service reports `depths` per
+        // ⭐ Say whether WHOLE records were delivered, so the record index can
+        // file them — what the config asked for, echoed: briefs when the query
+        // has a per-record source, whole records otherwise. (The service reports
+        // `whole` per
         // key and overrides this with what it actually served.)
-        const depth = request.depth === 'brief' || request.depth === 'full' ? request.depth : undefined
-        return depth ? { data: data ?? [], meta: { depth } } : { data: data ?? [] }
+        const whole = typeof request.whole === 'boolean' ? request.whole : undefined
+        return whole === undefined ? { data: data ?? [] } : { data: data ?? [], meta: { whole } }
       } catch (error) {
         if (error?.name === 'AbortError') {
           return { data: [], error: 'aborted' }
@@ -270,7 +271,9 @@ function toQuestion(request) {
   const sort = sortToWire(request.sort)
   if (sort) q.sort = sort
   if (typeof request.limit === 'number' && request.limit > 0) q.limit = request.limit
-  if (request.depth === 'brief' || request.depth === 'full') q.depth = request.depth
+  // ⛔ ONLY WHEN TRUE. The brief is the default and absent means the brief, so
+  // sending `whole: false` would be noise on every list question the client makes.
+  if (request.whole === true) q.whole = true
   // ⭐ `cursor` is the ONLY field here that is not the author's: it is opaque and
   // it comes from a previous answer's `cursors` (the records contract §2). ⛔ And
   // `exhaustive` deliberately does NOT cross — it is a client instruction about
@@ -385,7 +388,10 @@ async function flushAsked(url, queue, doFetch) {
   }
   const data = parsed && typeof parsed.data === 'object' && parsed.data ? parsed.data : {}
   const errors = parsed && typeof parsed.errors === 'object' && parsed.errors ? parsed.errors : {}
-  const depths = parsed && typeof parsed.depths === 'object' && parsed.depths ? parsed.depths : {}
+  // ⭐ `whole[key]` is present only for keys delivered as WHOLE entities — so a
+  // key's ABSENCE is the brief, and a key present that never asked is the
+  // brief-less Model saying so. Absent entirely when every key is briefs.
+  const wholes = parsed && typeof parsed.whole === 'object' && parsed.whole ? parsed.whole : {}
   // Both absent when empty, never `{}` (the records contract §5).
   const cursors = parsed && typeof parsed.cursors === 'object' && parsed.cursors ? parsed.cursors : {}
   const limits = parsed && typeof parsed.limits === 'object' && parsed.limits ? parsed.limits : {}
@@ -413,9 +419,9 @@ async function flushAsked(url, queue, doFetch) {
       entry.resolve({ data: null, error: `the records service answered without the key "${key}"` })
       return
     }
-    const depth = depths[key] === 'brief' || depths[key] === 'full'
-      ? depths[key]
-      : (entry.request.depth === 'brief' || entry.request.depth === 'full' ? entry.request.depth : undefined)
+    const whole = typeof wholes[key] === 'boolean'
+      ? wholes[key]
+      : (typeof entry.request.whole === 'boolean' ? entry.request.whole : undefined)
 
     const cursor = typeof cursors[key] === 'string' && cursors[key] ? cursors[key] : null
     const bound = typeof limits[key] === 'number' ? limits[key] : undefined
@@ -429,17 +435,17 @@ async function flushAsked(url, queue, doFetch) {
         ? entry.request.maxPages
         : DEFAULT_MAX_PAGES
       if (page <= cap) {
-        pending.set(entry, { cursor, collected: acc, page, depth, bound })
+        pending.set(entry, { cursor, collected: acc, page, whole, bound })
         return
       }
       // The caller's own bound, not the service's: report rather than spin.
-      entry.resolve({ data: acc, meta: withMeta({ depth, bound, partial: true, pages: cap }) })
+      entry.resolve({ data: acc, meta: withMeta({ whole, bound, partial: true, pages: cap }) })
       return
     }
 
     const collected = entry.collected ? entry.collected.concat(Array.isArray(rows) ? rows : []) : rows
     const meta = withMeta({
-      depth,
+      whole,
       bound,
       // ⭐ ONE FLAG, MEANING **NOT THE WHOLE POPULATION** — asked for by name, so
       // a caller has one boolean to branch on rather than three signals to

package/src/document-tracking.js

@@ -54,7 +54,7 @@
  * ## No page-level opt-in, deliberately
  *
  * `section_view` needs one (`trackSections`) because its dimension is unbounded
- * — a site's section types run to the hundreds and hosting capped the
+ * — a site's section types run to the hundreds and a host capped the
  * cardinality. **An outbound hostname is bounded by how many external sites a
  * page links to**, which is small and does not grow with the site.
  *

package/src/foundation-loader.js

@@ -32,8 +32,8 @@ function resolveAgainstDocument(url) {
  * ⭐ **Exported for the test, and the test exists because a HOST builds on this.**
  * The skip below is what lets a shell put the stylesheet in the head itself —
  * so the sheet applies during HTML parse instead of waiting for the runtime to
- * boot, parse `__DATA__` and inject it. Hosting shipped that on the strength of
- * this guard (the hosting lane, 2026-08-19); until then nothing
+ * boot, parse `__DATA__` and inject it. A host shipped that on the strength of
+ * this guard (2026-08-19); until then nothing
  * asserted it, so a refactor would have produced two `<link>` tags and two
  * fetches on their lane with every test here still green.
  *

package/src/page-renderer.js

@@ -128,8 +128,8 @@ export async function prefetchAndHydrate({ website, content, route, locale = nul
   // ⛔ THE TRANSPORT IS REQUIRED HERE, unlike on `prefetchPageData`, and this is the
   // one place the difference matters.
   //
-  // A function does NOT survive every isolate boundary. Measured by hosting under
-  // `wrangler dev` against a real Worker Loader, 2026-09-03: passed through an
+  // A function does NOT survive every isolate boundary. Measured by a host against
+  // a real isolate loader, 2026-09-03: passed through an
   // entrypoint's `fetch(Request)` with a JSON body the transport arrives
   // **`undefined`**; passed as an argument to an RPC method it arrives as a callable
   // function and the isolate invokes it. Only the RPC shape carries it.

package/src/prefetch.js

@@ -11,7 +11,8 @@
  * shape the datastore expects — a copy of the runtime's logic, in another repo, drifting
  * (the records envelope went silently unread that way on 2026-09-02). [Diego, 2026-09-03]:
  * *the backend sets the records service; the fetch comes from the runtime.* The host now calls
- * this and carries no copy. Hosting agreed to exactly that shape the same day.
+ * this and carries no copy; the host that renders in an isolate agreed to exactly
+ * that shape the same day.
  *
  * ⛔ Contract with the host, deliberately small:
  *   - `content`  the render payload (`site-content.json` / `__DATA__`), config included —
@@ -22,8 +23,8 @@
  *                decides how a site-relative one is reached (its origin, a binding).
  *                ⛔ **Crossing an isolate boundary, this survives only as an RPC method
  *                argument.** Through an entrypoint's `fetch(Request)` with a serialized
- *                body it arrives `undefined` (hosting, measured under `wrangler dev`
- *                against a real Worker Loader, 2026-09-03) — and the fetcher then falls
+ *                body it arrives `undefined` (measured by a host against a real
+ *                isolate loader, 2026-09-03) — and the fetcher then falls
  *                back to `globalThis.fetch`, so the request leaves from the isolate,
  *                outside whatever budget the host wrapped around it. `prefetchAndHydrate`
  *                refuses a non-function for exactly this reason; this entry keeps the
@@ -43,7 +44,7 @@
  *                deferred it to the browser with `prerender: false`). `hydrateDataStore`
  *                takes the list as-is and hydrates only `fetched` entries — a host reads the
  *                outcomes to tell "nothing was tried" from "everything tried failed", which
- *                is a different cache decision (hosting, 2026-09-03).
+ *                is a different cache decision (measured by a host, 2026-09-03).
  *
  * It resolves nothing the host owns and models no host route layout: every address is
  * `{base}/…` from the payload, or the records service the host itself

package/src/shell/main.js

@@ -2,7 +2,8 @@
  * Runtime Shell Entry Point
  *
  * Standalone browser app that boots a Uniweb site from __DATA__ injected
- * by a dynamic backend (unicloud, PHP, etc.).
+ * by a dynamic backend (a Uniweb backend, PHP, anything that can render a
+ * page shell).
  *
  * This calls the same start() function that all sites use. When no
  * __FOUNDATION_CONFIG__ is embedded in the page, start() checks for

package/src/ssr-renderer.js

@@ -1,7 +1,7 @@
 /**
  * SSR Renderer
  *
- * Hook-free rendering pipeline for SSG (build) and cloud SSR (unicloud).
+ * Hook-free rendering pipeline for SSG (build) and server-side SSR.
  * Mirrors BlockRenderer.jsx + Background.jsx using React.createElement
  * directly — no hooks, no JSX, no browser APIs.
  *
@@ -363,7 +363,7 @@ export function renderLayout(page, website) {
  * Construct a Uniweb singleton scoped to a single locale.
  *
  * Combines the three steps that every SSR consumer (browser SPA, Node
- * SSG, Cloudflare Worker SSR) needs in the same order: slice the
+ * SSG, a server-side isolate) needs in the same order: slice the
  * multi-locale content payload, run `initPrerender` (which builds the
  * Website + wires foundation capabilities), then `setActiveLocale` so
  * `website.activeLang` stays in sync with what the page is rendering
@@ -396,10 +396,10 @@ export function initPrerenderForLocale(content, foundation, locale, extensionsOr
  *
  * Returns the configured uniweb instance. Consumers can add extras after:
  * - Build: pre-populate DataStore, load extensions
- * - Unicloud: (none needed — payload is complete)
+ * - A server-side renderer: (none needed — the payload is complete)
  *
  * NOTE: Does NOT clone content. Cloning is the consumer's responsibility
- * (build modifies content before init; unicloud clones upfront).
+ * (build modifies content before init; a server-side renderer clones upfront).
  *
  * @param {Object} content - Site content JSON (pages, config, hierarchy)
  * @param {Object} foundation - Loaded foundation module

package/src/wire-foundation.js

@@ -119,10 +119,10 @@ export function wireFoundationCapabilities(uniweb, foundation) {
  * each `dist/{locale}/site-content.json` separately) get pass-through
  * behavior.
  *
- * The shape comes from the editor's publish payload, which is the
- * production canonical for multi-locale content (the Cloudflare Worker
- * SSR path consumes it directly). Build-time SSG pre-flattens to one
- * file per locale and so falls into the pass-through case.
+ * The shape comes from the editor's publish payload, which is the canonical
+ * form for multi-locale content — a server-side renderer consumes it
+ * directly. Build-time SSG pre-flattens to one file per locale and so falls
+ * into the pass-through case.
  *
  * @param {Object} content - Site content payload, possibly multi-locale.
  * @param {string} locale - Requested locale code.
@@ -152,10 +152,10 @@ export function sliceContentForLocale(content, locale) {
  * value MUST be wrapped as `{ data }` — otherwise the dispatcher's
  * lookup at `_dataStore.get(deriveCacheKey(request))` misses every
  * time and `cached.data` reads `undefined`. Three call sites used to
- * inline this loop independently (browser SPA, Node SSG, Cloudflare
- * Worker SSR); the Cloudflare one was using the wrong shape, silently
- * killing prefetched-data reuse in production. This helper is the one
- * canonical implementation.
+ * inline this loop independently (browser SPA, Node SSG, and a server-side
+ * renderer); one of the three was using the wrong shape, silently killing
+ * prefetched-data reuse wherever it ran. This helper is the one canonical
+ * implementation.
  *
  * @param {import('@uniweb/core').Website} website
  * @param {Array<{config: Object, data: any}>} fetchedData