@uniweb/core 0.29.6 → 0.29.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/core",
-  "version": "0.29.6",
+  "version": "0.29.8",
   "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
   "type": "module",
   "exports": {

package/src/data-paths.js

@@ -4,8 +4,8 @@
  *
  * ⚠️ `<name>` IS A QUERY'S NAME. `/data/<name>.json` is a named query's
  * MATERIALIZATION — the answer when no host declares a live lane — and never the
- * definition of anything. The records themselves live in `entities/{schema}/`,
- * and `records.yml` decides which of them are published.
+ * definition of anything. The records themselves are the files in
+ * `records/{schema}/` — every file there is one.
  *
  * Why this module exists. The path `/data/<name>.json` was a bare string
  * literal in six places across three packages: the build wrote it

package/src/fetch-config.js

@@ -684,7 +684,7 @@ function bindWhere(where, variables) {
 /**
  * ⭐ `scope:` IS ITS OWN FIELD, on both lanes. The service takes it natively; on
  * the compiled file the evaluators apply it to each record's placement (`path`,
- * the folder `records.yml` put it in) — `@uniweb/core`'s `applyScope`, the one the
+ * the folder `records/folder.yml` put it in) — `@uniweb/core`'s `applyScope`, the one the
  * build uses too. ⛔ Until 2026-09-11 it was folded here into
  * `where: { path: { under } }`, an authored form that is now retired in its
  * favour [Diego]: a branch is a scope, and `where` stays the author's predicate.

package/src/route-match.js

@@ -539,7 +539,7 @@ export function fillRoutePattern(pattern, values) {
     // A catch-all is filled from the record's placement and handle — the split
     // rule in reverse (`joinPathCapture`) — with each SEGMENT encoded and the
     // slashes between them kept as structure. `dir` is the placement; a record
-    // carries it as `path` (the folder `records.yml` put it in), which is why
+    // carries it as `path` (the folder `records/folder.yml` put it in), which is why
     // `path` here is read as the DIRECTORY and never as a composed capture.
     const handle = recordHandle(values)
     if (joinPathCapture({ dir: values.dir ?? values.path, slug: handle }) === null) return null

package/src/scope.js

@@ -2,7 +2,7 @@
  * A query's `scope:` — the folder branch it reads — evaluated over records that
  * carry their placement.
  *
- * A record's `path` is the folder `records.yml` placed it in (`build/src/site/
+ * A record's `path` is the folder `records/folder.yml` placed it in (`build/src/site/
  * query-processor.js`). A scope contains that folder and every folder below it, at
  * SEGMENT boundaries: `field` holds `field` and `field/2025`, never `fieldwork`.
  * The root (`''`) holds everything.