@uniweb/build 0.26.0 → 0.26.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -59,17 +59,17 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
+    "@uniweb/semantic-parser": "^1.3.1",
     "@uniweb/theming": "^0.1.15",
     "@uniweb/schemas": "^0.2.10",
-    "@uniweb/semantic-parser": "^1.3.1",
-    "@uniweb/projections": "^0.3.5",
+    "@uniweb/projections": "^0.3.6",
     "@uniweb/content-writer": "^0.3.4"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.12.10",
+    "@uniweb/runtime": "^0.12.13",
     "@uniweb/schemas": "^0.2.10",
-    "@uniweb/semantic-parser": "^1.3.1",
-    "@uniweb/content-reader": "^1.2.4"
+    "@uniweb/content-reader": "^1.2.4",
+    "@uniweb/semantic-parser": "^1.3.1"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -78,7 +78,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.12.0"
+    "@uniweb/core": "^0.12.1"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/site/schemaless-data.js

@@ -25,15 +25,13 @@
  *
  * ⇒ **Do not reintroduce a bundle here.** One object per file is what the
  * reader's static arm already assumes: a plain object GET on the verbatim tail,
- * with nothing anywhere that unbundles. Full account, including the endpoint
- * contract: `kb/framework/build/data-ball-retirement.md`.
+ * with nothing anywhere that unbundles.
  *
  * **A search index used to ride here too, and deliberately no longer does**
  * (2026-08-01). Only a CLI deploy produced one — a CMS publish produced none —
  * so a site's search existed or vanished depending on who published it, which
  * is the artifact-flicker rule exactly. A host that wants search derives it from
- * the content it already stores. See the note at the removal point below and
- * `collab/context/site-derived-artifacts.md`.
+ * the content it already stores. See the note at the removal point below.
  */
 
 import { existsSync } from 'node:fs'

package/src/uwx/sync-package.js

@@ -146,8 +146,8 @@ function walkEntityAssets(node, visitor) {
 //     dropping `src` only forces that at the cost of a migration window across
 //     two consumer chains where images blank.
 //
-//     ⇒ **Keep writing both.** See `kb/framework/content/asset-url-resolution.md`
-//     item 13 — and re-read it there rather than re-deriving the answer here.
+//     ⇒ **Keep writing both.** Settled 2026-08-* against the two consumer
+//     chains above; do not re-derive it from one of them in isolation.
 //
 // ⇒ Writing both means content authored now stays correct whichever order the
 // halves arrive in — the same reason the app writes both. The URL is dropped