uniweb 0.38.0 → 0.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.38.0",
+  "version": "0.40.0",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/core": "^0.17.0",
-    "@uniweb/kit": "^0.15.4",
+    "@uniweb/core": "^0.19.0",
+    "@uniweb/kit": "^0.15.6",
     "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/runtime": "^0.13.6"
+    "@uniweb/runtime": "^0.14.0"
   },
   "peerDependencies": {
+    "@uniweb/build": "^0.36.0",
     "@uniweb/content-reader": "^1.2.4",
-    "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/build": "^0.34.0"
+    "@uniweb/semantic-parser": "^1.4.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -851,7 +851,7 @@ team:
 
 You can keep the same declarations under `queries:` in `site.yml` instead, if you would rather have one file.
 
-**Show a query on a page** with `data:` in `page.yml` (the whole result), or `fetch:` in a section's frontmatter (a subset):
+**Show a query on a page** with `data:` in `page.yml` (the whole result), or `fetch:` in a section's frontmatter (a subset). A list — `data: [team, articles]` — declares several, each arriving under its own `content.data` key:
 
 ```yaml
 # pages/blog/page.yml          |   # a section on the homepage

package/src/commands/register.js

@@ -653,7 +653,25 @@ async function runRegister(args = []) {
           `  ${colors.dim}Supply a registry bearer with --token <bearer> (or UNIWEB_TOKEN); an existing one may be wrong or expired.${colors.reset}`
         )
       }
-      if (rawBody) log(`  ${colors.dim}${rawBody.slice(0, 500)}${colors.reset}`)
+      // ⭐ **Surface `detail` as a sentence, not as a JSON dump.** The registry
+      // answers with problem+json (RFC 9457), and its `detail` is written for a
+      // human — it carries the actual next step, which for a rejected
+      // re-register is "bump the version". Printing the whole body dimmed put
+      // that sentence inside a blob, at the end of a 500-char truncation, in the
+      // one moment the reader most needs it.
+      //
+      // ⚖️ Keyed on the SHAPE, not on any particular code: a new refusal the CLI
+      // has never seen explains itself the day the backend ships it, with no
+      // release here. That is the property worth having — this branch exists
+      // because a 422 the CLI did not know about arrived exactly that way.
+      if (parsedBody?.detail) {
+        log(`  ${parsedBody.detail}`)
+        if (parsedBody.code) {
+          log(`  ${colors.dim}(${parsedBody.code})${colors.reset}`)
+        }
+      } else if (rawBody) {
+        log(`  ${colors.dim}${rawBody.slice(0, 500)}${colors.reset}`)
+      }
       return { exitCode: 1 }
     }
   }

package/src/framework-index.json

@@ -1,16 +1,16 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-09-02T18:47:18.047Z",
+  "generatedAt": "2026-09-03T00:30:06.307Z",
   "packages": {
     "@uniweb/api": {
-      "version": "0.2.3",
+      "version": "0.2.5",
       "path": "framework/api",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/build": {
-      "version": "0.34.0",
+      "version": "0.36.0",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -34,7 +34,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.17.0",
+      "version": "0.19.0",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -47,14 +47,14 @@
       "deps": []
     },
     "@uniweb/icons": {
-      "version": "0.4.8",
+      "version": "0.4.10",
       "path": "framework/icons",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/kit": {
-      "version": "0.15.4",
+      "version": "0.15.6",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -73,7 +73,7 @@
       "deps": []
     },
     "@uniweb/projections": {
-      "version": "0.5.5",
+      "version": "0.5.7",
       "path": "framework/projections",
       "deps": [
         "@uniweb/content-writer",
@@ -81,7 +81,7 @@
       ]
     },
     "@uniweb/runtime": {
-      "version": "0.13.6",
+      "version": "0.14.0",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -119,7 +119,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.9.0",
+      "version": "0.9.2",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",

package/src/utils/conformance.js

@@ -162,10 +162,30 @@ export function formatConformanceWarning(result, siteDir = '') {
   const total = violations.length + setupErrors.length
   if (total === 0) return null
 
-  const headline =
-    `${total} content record${total === 1 ? '' : 's'} ` +
-    `${total === 1 ? 'does' : 'do'} not match the schemas ` +
-    `${c.bold}${result.foundation}${c.reset} declares.`
+  // ⛔ **Two different kinds of finding share this block, and one sentence cannot
+  // describe both.** A `violation` is a record whose VALUE disagrees with a
+  // schema. A `setupError` is data that could not be read, or that never reached
+  // the section meant to read it — *no record is involved*. Counting the second
+  // as "content records that do not match" sends the reader hunting through their
+  // data for a fault that is in their configuration, which is the worse of the
+  // two searches and the one that ends in "the framework is wrong".
+  //
+  // The total still leads the block; only the naming is split.
+  const parts = []
+  if (violations.length > 0) {
+    parts.push(
+      `${violations.length} content record${violations.length === 1 ? '' : 's'} ` +
+        `that ${violations.length === 1 ? 'does' : 'do'} not match the schemas ` +
+        `${c.bold}${result.foundation}${c.reset} declares`
+    )
+  }
+  if (setupErrors.length > 0) {
+    parts.push(
+      `${setupErrors.length} problem${setupErrors.length === 1 ? '' : 's'} ` +
+        `with how data reaches your sections`
+    )
+  }
+  const headline = `Found ${parts.join(' and ')}.`
 
   const lines = [
     // A finding on the record itself carries no `field` — "expected a list of