uniweb 0.50.0 → 0.51.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.50.0",
+  "version": "0.51.1",
   "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": "^0.25.1",
-    "@uniweb/kit": "^0.18.3",
-    "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/runtime": "^0.20.1"
+    "@uniweb/core": "^0.26.1",
+    "@uniweb/kit": "^0.18.4",
+    "@uniweb/runtime": "^0.20.3",
+    "@uniweb/semantic-parser": "^1.4.0"
   },
   "peerDependencies": {
-    "@uniweb/build": "^0.46.0",
+    "@uniweb/build": "^0.47.0",
     "@uniweb/content-reader": "^1.2.4",
     "@uniweb/semantic-parser": "^1.4.0"
   },

package/partials/agents.md

@@ -697,7 +697,7 @@ What can actually *read* it depends on where you deploy, because reading it need
 
 The artifacts **your build emits** to describe the public site never name them — `llms.txt`, the per-page `.md` projections, and the search index all describe pages a visitor reads, and a knowledge page's prose was written for the assistant instead. Two settings **outrank** `knowledge:`, so a contradiction resolves toward the narrower reach: `agents.exclude` in `site.yml`, and any `_`-prefixed route segment. *(A host that derives these artifacts itself, rather than serving the ones your build produced, applies its own rules — ask your host what it does with `knowledge:` before relying on it there.)*
 
-Don't confuse it with the visibility flags: `hidden: true` is a **draft** (not published at all), `hideIn` only controls **nav placement** (still reachable by URL), and `knowledge: true` is a **different audience** (never rendered for anyone).
+Don't confuse it with the visibility flags: `hidden: true` is a **draft** (not published at all), `hideIn` only controls **nav placement** (still reachable by URL), and `knowledge: true` is a **different audience** (never rendered for anyone). ⛔ `hidden: true` on `pages/404/` means a **draft 404** — it is not published and the site falls back to the generic `404.html`; an authored 404 needs no flag, since it is never listed in navigation anyway.
 
 **A site can be nothing but knowledge — that is a real and useful shape.** A site is a set of routes; it does not have to have HTML pages. Mark the root `knowledge: true` and every page inherits it, so the site renders nothing at all and exists to *be* an agent: a `/_agent/chat` URL that a web app, a mobile app, or someone else's backend sends requests to.
 
@@ -897,7 +897,7 @@ pages/blog/
 
 `entities/article/design-tips.md` becomes `/blog/design-tips`. The section inside `[slug]/` needs no special markdown — the matched record is delivered to it. Generated pages are excluded from navigation menus.
 
-**Which query the URL narrows — the page's route query:** the `[slug]` page's own `query:`, else its parent page's (the usual shape, above), else `site.yml`'s; if none declares one, the query its sections all declare. The first query of that level wins. Every section the route query reaches gets the one record; a section declaring a *different* query of its own gets that query as declared. The folder name says what the URL segment matches: `[slug]` the record's handle (`$name`, which compiled records carry — equal to their `slug`), `[uuid]` its `$uuid`, any other `[name]` the record's own field of that name. A folder inside `[slug]/` (`[slug]/cv/` → `/blog/:slug/cv`) is a parametric page too, reading the record when `[slug]/page.yml` declares the query. `[dir]` and `[path]` are refused as folder names, and so is any folder inside `[...path]/`.
+**Which query the URL narrows — the page's route query:** the `[slug]` page's own `query:`, else its parent page's (the usual shape, above), else `site.yml`'s; if none declares one, the query its sections all declare. The first query of that level wins. Every section the route query reaches gets the one record; a section declaring a *different* query of its own gets that query as declared. The folder name says what the URL segment matches: `[slug]` the record's handle (`$name`, which compiled records carry — equal to their `slug`), `[uuid]` its `$uuid`, any other `[name]` the record's own field of that name — and when that field holds several values, **any member** matches (the record's own link is its first value). Routing by a field that is not unique picks one record and which one is not guaranteed; the build warns. A folder inside `[slug]/` (`[slug]/cv/` → `/blog/:slug/cv`) is a parametric page too, reading the record when `[slug]/page.yml` declares the query. `[dir]` and `[path]` are refused as folder names, and so is any folder inside `[...path]/`.
 
 > **The record arrives as a single-element array under the query key** — `content.data.recent[0]`, not `content.data.article`. The runtime never coerces it to an object and never synthesizes a singular key. See *Data* in Part 4.
 

package/src/backend/payment-handoff.js

@@ -9,12 +9,27 @@
  * the answer.
  *
  * ⛔ THERE IS NO PRE-FLIGHT, AND ADDING ONE BACK IS A REGRESSION. A
- * `GET …/can-go-live` probe used to run before go-live; it called a route no
- * backend serves, and it folded every failure — 404 included — into
- * "proceed". A check that answers "fine" when it cannot reach the server is not
- * a check, and it made the CLI assume a posture it has no business assuming. A
- * pre-flight also cannot be authoritative: the backend re-evaluates at publish
- * time regardless, so a second asker is a second producer of one decision.
+ * `can-go-live` probe used to run before go-live, and it folded every failure —
+ * 404 included — into "proceed". A check that answers "fine" when it cannot
+ * reach the server is not a check, and it made the CLI assume a posture it has no
+ * business assuming. A pre-flight also cannot be authoritative: the backend
+ * re-evaluates at publish time regardless, so a second asker is a second producer
+ * of one decision — which is the reason that would stand even if the probe had
+ * worked.
+ *
+ * ⚠️ **THIS COMMENT USED TO SAY THE PROBE "called a route no backend serves".
+ * That was FALSE, corrected 2026-09-12.** What it called was
+ * `/dev/site/{uuid}/can-go-live` — and the 404 came from the PATH being wrong,
+ * not from the capability being absent. So the probe never worked at any version
+ * that shipped it, and every failure was swallowed by the fold above, which is
+ * exactly why nobody noticed.
+ *
+ * ⭐ Kept as a warning about the SHAPE of the old justification, not just the
+ * fact: a correct rule was resting on a claim about another system that this
+ * repo cannot see, and the claim was wrong. The rule survives because its real
+ * reasons are local — the fold, and the second-producer argument. **If you find
+ * yourself defending a rule here with an assertion about what a server does,
+ * check it or drop it.**
  *
  * WHAT THE CLI KNOWS ABOUT PAYMENT: nothing. It opens whatever settlement URL
  * the backend hands it, VERBATIM — provider-agnostic, and route-agnostic. The

package/src/framework-index.json

@@ -1,16 +1,16 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-09-11T23:04:50.071Z",
+  "generatedAt": "2026-09-12T17:35:34.207Z",
   "packages": {
     "@uniweb/api": {
-      "version": "0.3.2",
+      "version": "0.3.3",
       "path": "framework/api",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/build": {
-      "version": "0.46.0",
+      "version": "0.47.0",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -34,7 +34,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.25.1",
+      "version": "0.26.1",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -47,14 +47,14 @@
       "deps": []
     },
     "@uniweb/icons": {
-      "version": "0.4.16",
+      "version": "0.4.17",
       "path": "framework/icons",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/kit": {
-      "version": "0.18.3",
+      "version": "0.18.4",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -74,7 +74,7 @@
       "deps": []
     },
     "@uniweb/projections": {
-      "version": "0.6.1",
+      "version": "0.6.2",
       "path": "framework/projections",
       "deps": [
         "@uniweb/content-writer",
@@ -82,7 +82,7 @@
       ]
     },
     "@uniweb/runtime": {
-      "version": "0.20.1",
+      "version": "0.20.3",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -110,7 +110,7 @@
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.12.5",
+      "version": "0.13.1",
       "path": "framework/templates",
       "deps": []
     },
@@ -120,7 +120,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.9.13",
+      "version": "0.9.15",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",