@uniweb/build 0.24.1 → 0.24.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.24.1",
+  "version": "0.24.3",
   "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/theming": "^0.1.15",
-    "@uniweb/projections": "^0.3.3",
-    "@uniweb/semantic-parser": "^1.2.3",
     "@uniweb/schemas": "^0.2.10",
-    "@uniweb/content-writer": "^0.3.3"
+    "@uniweb/semantic-parser": "^1.2.3",
+    "@uniweb/theming": "^0.1.15",
+    "@uniweb/content-writer": "^0.3.3",
+    "@uniweb/projections": "^0.3.3"
   },
   "optionalDependencies": {
-    "@uniweb/content-reader": "^1.2.3",
-    "@uniweb/runtime": "^0.12.1",
+    "@uniweb/schemas": "^0.2.10",
     "@uniweb/semantic-parser": "^1.2.3",
-    "@uniweb/schemas": "^0.2.10"
+    "@uniweb/runtime": "^0.12.2",
+    "@uniweb/content-reader": "^1.2.3"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",

package/src/site/build-site-data.js

@@ -126,8 +126,9 @@ export async function buildSiteData({
   //    in the vite plugin path that's fine because vite copies
   //    `public/` into `dist/` at build time. The link-mode pipeline
   //    has no vite, so we mirror that copy ourselves into
-  //    `<distDir>/data/` — the path `uniweb deploy::collectDataFiles`
-  //    walks at upload time. Same output bytes, same paths, just
+  //    `<distDir>/data/` — the set the CLI's `site-data-upload` lane walks at
+  //    publish time. (This named `uniweb deploy::collectDataFiles` until
+  //    2026-08-18; no such function has existed for some time.) Same output bytes, same paths, just
   //    without the vite intermediary.
   if (siteContent.config?.collections) {
     const collectionsBase = siteContent.config?.paths?.collections

package/src/site/index.js

@@ -42,7 +42,7 @@ export {
   writeCollectionFiles,
   getCollectionLastModified
 } from './collection-processor.js'
-export { assembleDataBall, collectBallAssets, rewriteBallAssets } from './data-ball.js'
+export { collectSchemalessData, collectSchemalessDataAssets, rewriteSchemalessDataAssets } from './schemaless-data.js'
 export {
   parseFetchConfig,
   executeFetch,

package/src/site/{data-ball.js → schemaless-data.js}

@@ -1,19 +1,39 @@
 /**
- * Data ball — the static-delivery half of a composite `uniweb deploy`. A site's
- * collections partition by schema presence: a collection that resolves a data schema
- * syncs as folder entities; a SCHEMA-LESS collection has no entity model, so its built
- * `dist/data/<name>.json` (cascade + any `deferred:` per-record files) is delivered
- * statically. This bundles that schema-less subset of `dist/data/**` into one JSON doc
- * the deploy uploads as a single content-addressed asset; the backend unwraps it into
- * the `/data/*` bytes the gateway serves.
+ * Schema-less collection data — the set, and its local media.
  *
- *   { data: { "<relpath-under-data>": <json> } }   // schema-less collections only
+ * ⭐ **The name carries the scope on purpose.** This is NOT "the site's static
+ * data" in general. A site's collections partition by **schema presence**: one
+ * that resolves a data schema syncs as folder entities — content a backend
+ * genuinely consumes, queryable, editable, with a `brief:` for its lean shape.
+ * A **schema-less** collection has no entity model, so its compiled
+ * `dist/data/<name>.json` (plus any `deferred:` per-record files) is delivered
+ * as files instead. That fallback tier is all this module is about.
  *
- * **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 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`.
+ *   { data: { "<relpath under dist/data>": <json> } }   // schema-less only
+ *
+ * ⇒ It is an **in-memory enumeration**, not an artifact. `collectSchemalessData`
+ * gathers the set; the CLI's `site-data-upload` lane PUTs each file to the
+ * target the backend returns, landing at its serving tail.
+ *
+ * ## ⛔ It used to be a "data ball", and that is retired (2026-08-18)
+ *
+ * This merged the whole set into ONE uploaded asset that the backend then had
+ * to fetch, parse and fan out. It was the **only aggregate the CLI produced** —
+ * media, foundation code and the runtime all upload one object per file — and
+ * the only place these bytes ever transited the backend. Nothing in the code or
+ * the docs ever justified the bundling.
+ *
+ * ⇒ **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`.
+ *
+ * **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`.
  */
 
 import { existsSync } from 'node:fs'
@@ -56,7 +76,7 @@ function collectionOf(relPath) {
  *        `emitSyncPackages(...).schemaless`); only these contribute `data`.
  * @returns {Promise<{ data: Object }|null>} null when there is nothing to deliver.
  */
-export async function assembleDataBall(distDir, schemalessNames = []) {
+export async function collectSchemalessData(distDir, schemalessNames = []) {
   const schemaless = new Set(schemalessNames)
   const allData = await readJsonTree(join(distDir, DATA_DIR))
   const data = {}
@@ -128,7 +148,7 @@ export async function assembleDataBall(distDir, schemalessNames = []) {
  * @param {{data:object}|null} ball
  * @returns {string[]} deduped refs to upload
  */
-export function collectBallAssets(ball) {
+export function collectSchemalessDataAssets(ball) {
   const refs = new Set()
   const walk = (n) => {
     if (typeof n === 'string') {
@@ -150,7 +170,7 @@ export function collectBallAssets(ball) {
  * @param {Record<string,string>} map - ref → serve URL
  * @returns {{data:object}|null} a new ball, or the input when there's nothing to do
  */
-export function rewriteBallAssets(ball, map) {
+export function rewriteSchemalessDataAssets(ball, map) {
   if (!ball || !map || Object.keys(map).length === 0) return ball
   const walk = (n) => {
     if (typeof n === 'string') return map[n] || n

package/src/uwx/collections.js

@@ -493,10 +493,16 @@ export async function buildCollectionEntities(siteRoot, opts = {}) {
       // soft skip — the collection is delivery-only, not a sync target. Only an
       // EXPLICIT schema/model the author asked for is a hard error.
       if (!decl.schemaExplicit) {
-        warnings.push(
-          `${name}: no data schema "${modelName}" (subfolder-name default) — not synced`
-        )
-        schemaless.push({ name })
+        // ⛔ Deliberately NOT a `warnings` string. This is a product decision the
+        // author is making — entities or static files — and it needs to be
+        // reported at a prominence a prose warning cannot carry. Callers get the
+        // structured entry and say it themselves (`cli/src/commands/{publish,push}.js`).
+        //
+        // It used to push `"… — not synced"`, printed dim among everything else.
+        // That was misleading in the expensive direction: the data IS delivered,
+        // as static files. An author read "not synced" as "my data did not
+        // upload" — or skimmed it — and either way could not act on it.
+        schemaless.push({ name, model: modelName })
         continue
       }
       throw new Error(

package/src/uwx/sync-package.js

@@ -121,9 +121,33 @@ function walkEntityAssets(node, visitor) {
 //   - **the id is what survives.** A URL is a host's route layout frozen into
 //     content that outlives it; an id is re-resolved on every render, so a host
 //     that moves its assets costs a config edit rather than a migration.
-//   - **the URL is what RENDERS today.** No deployment emits `config.assets.url`
-//     yet, so a resolver handed an id alone would resolve nothing. With the URL
-//     still there it falls through and renders exactly as before.
+//   - **the URL is what RENDERS today.** With the URL still there, a resolver
+//     that cannot resolve the id falls through and renders exactly as before.
+//
+//     ⚠️ **This bullet used to justify itself with "no deployment emits
+//     `config.assets.url` yet". FALSIFIED 2026-08-18** by the backend lane:
+//     `serve` publishes the pattern **unconditionally**, falling back to the
+//     direct form, so a deployment with no asset storage emits the honest
+//     `/gateway/asset/dist/{id}/base.{ext}` rather than nothing (measured by
+//     them on a running daemon, not read off a type). ⛔ Scoped to deployments
+//     running code from 2026-08-17 or later; an older one emits nothing, and
+//     absent stays absent. A present-tense negative about someone else's
+//     deployments is the claim nothing in this repo can ever contradict — it
+//     was true when written, and nothing here changed when it stopped being.
+//
+//     ⛔ **That does NOT license dropping the URL, and the reason is not
+//     coverage.** An earlier version of this note named coverage as the
+//     governor; it was only ever a gate. Dropping the `src` companion was
+//     **withdrawn as a goal** on 2026-08-17 on CONSUMER grounds: the editor
+//     canvas renders `attrs.url || attrs.src` and reads `assetId` nowhere, so
+//     an id-only node shows an `<img>` with no source *(measured by the
+//     frontend lane — their surface, their finding)*. Durability comes from
+//     every consumer PREFERRING the id, which each can do on its own schedule;
+//     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.
 //
 // ⇒ 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
@@ -213,7 +237,7 @@ function rewriteEntityAssets(node, map, ids) {
  *   siteContent: { buffer, entityCount, index, models }|null,
  *   collections: { buffer, entityCount, index, models }|null,
  *   hashes: Object<string,string>, warnings: string[], skipped: number,
- *   schemaless: Array<{name: string}>, localAssets: string[] }>}
+ *   schemaless: Array<{name: string, model: string}>, localAssets: string[] }>}
  *   `schemaless` lists collections that resolved no data schema (soft-skipped from
  *   the sync) — the composite deploy delivers these statically via the data ball.
  *   `localAssets` lists the site-root local media refs (`/images/x.png`) the deploy