uniweb 1.15.0 → 1.15.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.15.0",
+  "version": "1.15.2",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -43,11 +43,11 @@
     "tar": "^7.0.0",
     "@uniweb/content-writer": "~1.3.0",
     "@uniweb/core": "~1.4.0",
-    "@uniweb/schemas": "~1.6.0",
+    "@uniweb/schemas": "~1.6.1",
     "@uniweb/semantic-parser": "~1.12.2"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.7.0",
+    "@uniweb/build": "~1.7.2",
     "@uniweb/content-reader": "~1.5.4",
     "@uniweb/semantic-parser": "~1.12.2"
   },

package/partials/agents.md

@@ -309,7 +309,7 @@ Paths are relative to the site package you identified in step 1 — `site/` in t
 
 **Change the brand color.** `<site>/theme.yml` → `colors.primary`. One line, and every component follows. Do **not** edit Tailwind color classes in components to change brand color — that is the exact anti-pattern this system removes.
 
-**Change how code blocks look.** `<site>/theme.yml` → `code:`. Name one of Shiki's 65 bundled themes (`code: dracula`), name one per scheme (`code: { light: github-light, dark: github-dark }`), or take a theme and adjust it (`code: { theme: github-dark, background: '#0D0D0D' }`). Hand-picking every syntax colour is possible and is the last thing to reach for.
+**Change how code blocks look.** `<site>/theme.yml` → `code:`. Name one of Shiki's 65 bundled themes (`code: dracula`), name one per scheme (`code: { light: github-light, dark: github-dark }`), or take a theme and adjust it (`code: { theme: github-dark, background: '#0D0D0D' }`). Hand-picking every syntax colour is possible and is the last thing to reach for. A block paints its theme's background and text colour before the highlighter loads when they are known — the default theme's, or the `background` and `foreground` the site declares — so declare both beside a named theme to paint them from the start.
 
 **Change a nav item.** First check how nav is produced. If `<site>/layout/header.md` lists the links (a markdown list, or a `yaml:nav` block), edit it there. If it doesn't, the Header is generating nav from the page hierarchy — change page titles and order in `site.yml` / `page.yml` instead.
 
@@ -1173,7 +1173,7 @@ Header.className = 'p-0'
 Header.as = 'header'
 ```
 
-**A header that stays in view is a setting, not a class.** `sticky top-0` on your component's markup does nothing: a sticky element moves only within its parent, and the section's wrapper and the area's are as tall as your header. Declare `sticky: true` in the type's `meta.js` — an author turns it off with `sticky: false` — and the runtime makes sticky the box that can stay in view. A section in the body sticks the same way, and `sticky: { default: true, top: 'var(--header-height)' }` keeps one below the header. A layout of your own that wraps an area in an element makes that element sticky when `page.isSticky('header')`. `uniweb dev` names a sticky element that cannot move in the console.
+**A header that stays in view is a setting, not a class.** `sticky top-0` on your component's markup does nothing: a sticky element moves only within its parent, and the section's wrapper and the area's are as tall as your header. Declare `sticky: true` in the type's `meta.js` — an author turns it off with `sticky: false` — and the runtime makes sticky the box that can stay in view. A section in the body sticks the same way and stays below the stuck header by itself: the runtime measures how far the header reaches and publishes it as `--uw-sticky-top` (a type's `top` overrides it). A link to a section lands below the stuck header too. A child section in kit's `<ChildGrid>` stays in view beside the column it sits next to, and on a phone, at one column, scrolls with the page. A sticky section inside a box with `overflow: hidden` cannot stick — clip with `overflow: clip`. A layout of your own that wraps an area in an element makes that element sticky when `page.isSticky('header')`. `uniweb dev` names a sticky element that cannot move in the console.
 
 ### meta.js
 
@@ -3082,7 +3082,7 @@ Most Uniweb failures are **silent** — the build succeeds and the page is wrong
 
 **A var in frontmatter does nothing** — component vars only apply when declared in that section type's `meta.js` `vars:`. Unknown names are ignored silently.
 
-**A sticky header scrolls away** — it is `sticky top-0` on the component's own markup, which has no room to move. Make the section sticky instead: `sticky: true` in its type's `meta.js`. `uniweb dev` names the element in the console.
+**A sticky header scrolls away** — it is `sticky top-0` on the component's own markup, which has no room to move. Make the section sticky instead: `sticky: true` in its type's `meta.js`. A sticky section that still scrolls away sits in a box with `overflow: hidden` — clip with `overflow: clip`. `uniweb dev` names the element in the console.
 
 Loud failures:
 

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-20T03:11:00.010Z",
+  "generatedAt": "2026-10-20T04:47:12.392Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.2"
     },
     "@uniweb/build": {
-      "version": "1.7.0"
+      "version": "1.7.2"
     },
     "@uniweb/content-reader": {
       "version": "1.5.4"
@@ -24,7 +24,7 @@
       "version": "1.0.5"
     },
     "@uniweb/kit": {
-      "version": "1.5.3"
+      "version": "1.6.0"
     },
     "@uniweb/loom": {
       "version": "1.1.0"
@@ -36,13 +36,13 @@
       "version": "1.1.6"
     },
     "@uniweb/runtime": {
-      "version": "1.1.13"
+      "version": "1.1.15"
     },
     "@uniweb/scene": {
       "version": "1.0.1"
     },
     "@uniweb/schemas": {
-      "version": "1.6.0"
+      "version": "1.6.1"
     },
     "@uniweb/scholar": {
       "version": "1.1.0"
@@ -57,7 +57,7 @@
       "version": "1.1.4"
     },
     "@uniweb/theming": {
-      "version": "1.2.0"
+      "version": "1.2.1"
     },
     "@uniweb/unipress": {
       "version": "1.1.11"