@uniweb/build 0.64.0 → 0.64.2

package/src/uwx/sync-package.js

@@ -359,6 +359,11 @@ export async function emitSyncPackages(siteRoot, opts = {}) {
         // …and the same data schema, where a name stands for the type of its data key
         // (`@/team` → `@/member`, `data-key-types.js`): decided once, by the records.
         keyTyped: col.keyTyped,
+        // …and whether this deployment takes the key that says so (`siteContent.queryFields`) —
+        // and the page and `settings` keys that carry Open Graph texts per language.
+        ...(Array.isArray(opts.queryFields) ? { queryFields: opts.queryFields } : {}),
+        ...(Array.isArray(opts.pageFields) ? { pageFields: opts.pageFields } : {}),
+        ...(Array.isArray(opts.settingsFields) ? { settingsFields: opts.settingsFields } : {}),
         // Withhold the `$services`/`$secrets` Sections when the caller has
         // determined the file is not asking for anything new by them. Passed
         // through rather than decided here: the last-agreed state is project
@@ -517,6 +522,21 @@ export async function emitSyncPackages(siteRoot, opts = {}) {
   }))
   const changedRecords = recordChanged.filter((r) => r.changed)
 
+  // ⛔ A RECORD THAT LOST ITS IDENTITY IS NOT UNCHANGED. Its hash was banked for this backend,
+  // so a push to it succeeded — and wrote the record's `$uuid` into its file — yet it goes with no
+  // `$uuid` now: the line is gone from the file. Skipped as unchanged, the folder still named it,
+  // by `$ref`, and the backend refused a reference to a record the package does not carry
+  // (measured 2026-09-26); sent, it would be a second record. A pull writes it back.
+  const refusals = [...(col.refusals || [])]
+  for (const r of recordChanged) {
+    if (r.changed || r.entity.document.$uuid) continue
+    refusals.push(
+      `${r.entity.id}: its \`$uuid\` is gone from its file, though it was pushed to this backend ` +
+        'before — sent as it is, it would be a second record. Run `uniweb pull`, which writes it ' +
+        'back, then push.'
+    )
+  }
+
   let records = null
   // ⭐ A RECORD THAT NAMES A RECORD THIS PUSH CREATES names it by `$ref`
   // (`records.js::encodeReference`), and the backend stores the uuid it mints for it. The
@@ -572,6 +592,9 @@ export async function emitSyncPackages(siteRoot, opts = {}) {
   // banked is then, by construction, what was hashed. A future injection is covered
   // by adding one line here — not by finding every reader.
   const applied = {
+    ...(Array.isArray(opts.queryFields) ? { queryFields: opts.queryFields } : {}),
+    ...(Array.isArray(opts.pageFields) ? { pageFields: opts.pageFields } : {}),
+    ...(Array.isArray(opts.settingsFields) ? { settingsFields: opts.settingsFields } : {}),
     ...(assetRewrite ? { assetRewrite } : {}),
     ...(assetIds ? { assetIds } : {}),
     ...(injectInfo ? { injectInfo } : {}),
@@ -582,7 +605,7 @@ export async function emitSyncPackages(siteRoot, opts = {}) {
     siteContent, records, siteContentUuid, hashes, warnings, skipped,
     // Records that name a record this push creates — see `namesNew` above.
     namesNew,
-    refusals: col.refusals || [],
+    refusals,
     schemaless: col.schemaless, localAssets, applied,
     // { stamped, unknown } when identity was applied; null when the caller passed
     // no map. `unknown > 0` with `stamped === 0` on a site that has been pushed

package/src/validate-data.js

@@ -206,10 +206,19 @@ export async function validateDataInputs({ siteRoot, foundationPath }) {
         // (pass 2). A list root was deferred here until then, though the query's records
         // are exactly that list.
 
+        // ⭐ WHAT THE QUERY'S RECORDS ARE, for a key typed by a schema whose root is a list: the
+        // list's ITEMS when the query selects other records (`@/link` records feeding `@/menu`), but
+        // ENTITIES of the list schema — each holding a whole list — when the query names that schema
+        // itself (`menus: { schema: '@/menu' }`). ⛔ Until 2026-09-26 both were checked as items, so
+        // every query over a list schema failed ("missing required field '[0].label'") and a push,
+        // which gates on this check, stopped.
+        const decl = typeof input.query === 'string' ? config.queries?.[input.query] : null
+        const querySchema = decl ? decl.schema ?? keyTypes.get(input.query) ?? `@/${input.query}` : undefined
+
         const pairKey = `${input.path} ${ref}`
         let entry = work.get(pairKey)
         if (!entry) {
-          entry = { path: input.path, ref, schema, users: [] }
+          entry = { path: input.path, ref, schema, users: [], entities: querySchema === ref }
           work.set(pairKey, entry)
         }
         entry.users.push({ route: page.route, section: type, key })
@@ -234,10 +243,11 @@ export async function validateDataInputs({ siteRoot, foundationPath }) {
     schemasSeen.add(entry.ref)
     const items = Array.isArray(records) ? records : [records]
 
-    // A schema whose ROOT IS A LIST describes the whole value the key receives, and the
-    // query's records ARE that list — so they are checked once, as the list. Any other
-    // schema describes one record, checked per record.
-    if (rootListSection(entry.schema)) {
+    // A schema whose ROOT IS A LIST describes the whole value the key receives, and a query of
+    // other records delivers that list — so they are checked once, as the list. Any other
+    // schema describes one record, checked per record — and so are the entities of a list
+    // schema a query of that schema delivers, each holding its list (`validateItem`).
+    if (rootListSection(entry.schema) && !entry.entities) {
       recordCount += items.length
       const base = { file: entry.path, schema: entry.ref, users: entry.users }
       for (const finding of validateBound(entry.schema, items)) {