uniweb 1.19.0 → 1.19.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.19.0",
+  "version": "1.19.2",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,13 +41,13 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
+    "@uniweb/core": "~1.4.6",
     "@uniweb/content-writer": "~1.3.0",
-    "@uniweb/core": "~1.4.5",
     "@uniweb/schemas": "~1.6.5",
     "@uniweb/semantic-parser": "~1.13.0"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.9.0",
+    "@uniweb/build": "~1.9.1",
     "@uniweb/content-reader": "~1.5.6",
     "@uniweb/semantic-parser": "~1.13.0"
   },

package/partials/agents.md

@@ -660,6 +660,9 @@ background: primary-900                                  # Palette token (bare n
 background:                                              # Object form for more control
   image: { src: /img.jpg, position: center top }
   overlay: { enabled: true, type: dark, opacity: 0.5 }
+
+background:
+  video: { src: /videos/hero.mp4, poster: /images/hero.jpg }   # the poster shows until the video plays
 ```
 
 Components that render their own background declare `background: 'self'` in `meta.js`, and the runtime then draws none; to draw the author's background themselves they render kit's `<SectionBackground block={block} />`.
@@ -1874,7 +1877,7 @@ const page = website.activePage
 | `block.themeName` | `"light"`, `"medium"`, `"dark"` |
 | `block.stableId` / `block.key` | Stable ID from filename or `id:` / unique key across pages — use as React key |
 | `block.path` | Page route this block belongs to |
-| `block.dataLoading` | True while declared data is still resolving |
+| `block.dataLoading` | True while declared data is still resolving — also on a pre-rendered page, for data the browser fetches, so the loading state is what that page first shows |
 | `block.dataError` | `{ <key>: message }` when the fetch filling a declared key FAILED, else `null`. A failed key is `null` in `content.data` — never `[]`, which means "no records" |
 
 ```jsx
@@ -1959,7 +1962,7 @@ fetch:
 
 **Lean lists.** A list carries each record's brief, so heavy parts belong in a section of their own — `@std/article`'s body is `body` — and never ride a list. A section that shows them declares its key `whole: true`; elsewhere components fetch the whole record on demand with `useWholeRecord(record, { query })`, which returns it as stored — `full.body.content`. Every file-based record gets its own file, `/data/<name>/<name of the record>.json`. An external query's whole record comes from its `record:` request, below. (`deferred:` is removed — the build stops on it.) The hook is safe to call on any query: when the query has no separate source for one record it returns the record you passed in.
 
-**Component-side fetching.** When a component genuinely needs to fetch on its own (a search box, "load more", a lazy popover), use the kit hooks — `useFetched`, `useCacheEntry`, `useWholeRecord`. They share the framework's cache and dispatcher with declarative fetches; same-key requests dedupe automatically.
+**Component-side fetching.** When a component genuinely needs to fetch on its own (a search box, "load more", a lazy popover), use the kit hooks — `useFetched`, `useCacheEntry`, `useWholeRecord`. They share the framework's cache and dispatcher with declarative fetches; same-key requests dedupe automatically. On a pre-rendered page a hook's first render finds only what that page's own data holds — a declared key's answer, or its page's or the site's `fetch:`. Anything else is pre-rendered as the hook's loading state and fetched by the browser after it loads, so declare a key (`data:` in `meta.js`) for whatever a page must show without JavaScript.
 
 **Validate before shipping.** `uniweb validate` checks file-based data against your declared schemas — missing required fields, type/enum/format mismatches, nested fields. A violation fails it (`--lax` only reports); it checks every record file in `records/`, and `push` / `publish` refuse the same findings before sending anything. Distinct from `uniweb doctor` (project structure): `validate` checks your *data* against the schemas you *declared*. External queries (`url:`) are reported as deferred — their data isn't in the project; the value of a `ref`/`options` field is not checked against the entity it names.
 

package/src/commands/build.js

@@ -588,6 +588,9 @@ function resolveFoundationDir(projectDir, siteConfig) {
  * (dist/assets/), or static-host extras (sitemap, robots, search-index,
  * _pages/*) — `publish` reads none of them. ⛔ *It processed media into
  * dist/assets/ — WebP copies, video posters, PDF thumbnails — until 2026-10-19.*
+ * ⚠️ Except each extra language's `dist/<lang>/search-index.json`: the
+ * `buildLocalizedContent` step below writes one on this lane too, and nothing
+ * reads it (measured 2026-10-25).
  *
  * The `buildLocalizedContent` step is the same call bundle mode makes
  * post-vite, so multi-locale sites get identical per-locale outputs in

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-25T15:30:53.604Z",
+  "generatedAt": "2026-10-25T19:16:49.028Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.4"
     },
     "@uniweb/build": {
-      "version": "1.9.0"
+      "version": "1.9.1"
     },
     "@uniweb/content-reader": {
       "version": "1.5.6"
@@ -15,7 +15,7 @@
       "version": "1.3.0"
     },
     "@uniweb/core": {
-      "version": "1.4.5"
+      "version": "1.4.6"
     },
     "@uniweb/frame-bridge": {
       "version": "1.0.2"
@@ -36,7 +36,7 @@
       "version": "1.2.0"
     },
     "@uniweb/runtime": {
-      "version": "1.2.0"
+      "version": "1.2.2"
     },
     "@uniweb/scene": {
       "version": "1.0.1"