uniweb 0.51.0 → 0.51.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.51.0",
+  "version": "0.51.1",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -43,13 +43,13 @@
     "tar": "^7.0.0",
     "@uniweb/core": "^0.26.1",
     "@uniweb/kit": "^0.18.4",
-    "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/runtime": "^0.20.3"
+    "@uniweb/runtime": "^0.20.3",
+    "@uniweb/semantic-parser": "^1.4.0"
   },
   "peerDependencies": {
+    "@uniweb/build": "^0.47.0",
     "@uniweb/content-reader": "^1.2.4",
-    "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/build": "^0.47.0"
+    "@uniweb/semantic-parser": "^1.4.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

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,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-09-12T17:05:58.363Z",
+  "generatedAt": "2026-09-12T17:35:34.207Z",
   "packages": {
     "@uniweb/api": {
       "version": "0.3.3",
@@ -110,7 +110,7 @@
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.13.0",
+      "version": "0.13.1",
       "path": "framework/templates",
       "deps": []
     },
@@ -120,7 +120,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.9.14",
+      "version": "0.9.15",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",