uniweb 0.12.43 → 0.12.44

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.12.43",
+  "version": "0.12.44",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,14 +41,14 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/core": "0.7.17",
-    "@uniweb/runtime": "0.8.23",
-    "@uniweb/kit": "0.9.21"
+    "@uniweb/core": "0.7.18",
+    "@uniweb/kit": "0.9.22",
+    "@uniweb/runtime": "0.8.24"
   },
   "peerDependencies": {
+    "@uniweb/build": "0.14.26",
     "@uniweb/content-reader": "1.1.12",
-    "@uniweb/semantic-parser": "1.1.17",
-    "@uniweb/build": "0.14.25"
+    "@uniweb/semantic-parser": "1.1.17"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -1023,7 +1023,7 @@ fonts:
   mono: "'Fira Code', monospace"
 ```
 
-Because the site wires the families onto real elements, **components need no font-family classes** — render semantic markup (`<H1>`, `<P>`, `<code>` from the kit) and the roles apply. This is what lets one foundation re-font per site with zero code changes.
+Because the site wires the families onto real elements, **the norm is that a foundation doesn't set fonts itself** — render semantic markup (`<H1>`, `<P>`, `<code>` from the kit) and the roles apply. (It stays Tailwind for everything else — layout, spacing, weights, color.) That convention is what authors can count on: `body`/`heading`/`mono` control the fonts the same way in every foundation, and one foundation re-fonts per site with zero code changes.
 
 **Loading the files** — two site-side options, both config-only, neither adds a dependency:
 
@@ -1048,23 +1048,19 @@ fonts:
 
 **In a component, weight is yours; family is the site's.** Weight / size / style utilities (`font-bold`, `font-black`, `italic`, `text-xl`) are ordinary design vocabulary — use them freely. A font-**family** utility is only safe when the family behind it is site-controlled — and by default `font-sans` / `font-serif` are *not* (they resolve to Tailwind's built-in stacks; only `font-mono` tracks the site's `mono` role, by name-collision). So a bare `font-serif` in a component silently hardcodes a typeface.
 
-**A family beyond the three roles** — an editorial serif, a display face — is a **foundation var**, so the site keeps control. Name it after a Tailwind font slot (`font-serif`) and that utility resolves to it; or give it any name and reference the variable directly:
+**When a design needs typefaces the element convention can't express** — an editorial serif on selected prose, a mono for metadata labels that aren't `<code>` — a foundation manages those explicitly instead of deferring. It uses the `font-serif` / `font-mono` (or `font-sans`) utility and declares each family as a **foundation var**, so the family stays site-controlled. The var drives its utility, and the family **loads** (via `fonts.import` / `fonts.faces`) even though it isn't one of the three `body`/`heading`/`mono` role slots:
 
 ```js
-// foundation src/main.js
+// foundation src/main.js — typefaces this foundation manages itself.
+// Defaults are OS stacks, so it renders native until a site opts in.
 export const vars = {
-  'font-serif': {
-    default: "Georgia, 'Times New Roman', serif",
-    description: 'Editorial serif for pull-quotes, taglines, quotes',
-  },
+  'font-sans':  { default: 'ui-sans-serif, system-ui, sans-serif', description: 'Base — headlines, UI, body' },
+  'font-serif': { default: 'ui-serif, Georgia, serif', description: 'Editorial — blurbs, taglines, quotes' },
+  'font-mono':  { default: 'ui-monospace, SFMono-Regular, monospace', description: 'Metadata — labels, dates, code' },
 }
 ```
-```jsx
-<p className="font-serif">{content.tagline}</p>   {/* now site-controlled */}
-// …or a custom-named var:  <p style={{ fontFamily: 'var(--font-display)' }}>
-```
 
-The site sets the family in `theme.yml` under `vars:` (`font-serif: "Fraunces, Georgia, serif"`) and loads it with `fonts.import` / `fonts.faces` — the file loads even though the family isn't one of the three role slots.
+Components keep using `font-sans` / `font-serif` / `font-mono` unchanged; the site sets each family in `theme.yml` under `vars:` and loads it with `fonts.import` / `fonts.faces`. (A custom name like `font-display` has no built-in utility — reference it with `var(--font-display)`.)
 
 ### Foundation variables
 

package/src/framework-index.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-07-17T21:03:16.675Z",
+  "generatedAt": "2026-07-17T23:45:26.497Z",
   "packages": {
     "@uniweb/build": {
-      "version": "0.14.25",
+      "version": "0.14.26",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -25,7 +25,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.7.17",
+      "version": "0.7.18",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -43,7 +43,7 @@
       "deps": []
     },
     "@uniweb/kit": {
-      "version": "0.9.21",
+      "version": "0.9.22",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -61,7 +61,7 @@
       "deps": []
     },
     "@uniweb/runtime": {
-      "version": "0.8.23",
+      "version": "0.8.24",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -99,7 +99,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.4.32",
+      "version": "0.4.33",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",