uniweb 1.22.4 → 1.23.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.22.4",
+  "version": "1.23.1",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.3.2",
     "prompts": "^2.4.2",
     "tar": "^7.5.21",
-    "@uniweb/core": "~1.4.12",
     "@uniweb/schemas": "~1.6.7",
-    "@uniweb/content-writer": "~1.3.1",
-    "@uniweb/semantic-parser": "~1.13.0"
+    "@uniweb/core": "~1.5.0",
+    "@uniweb/semantic-parser": "~1.13.0",
+    "@uniweb/content-writer": "~1.3.1"
   },
   "peerDependencies": {
     "@uniweb/semantic-parser": "~1.13.0",
     "@uniweb/content-reader": "~1.5.7",
-    "@uniweb/build": "~1.11.4"
+    "@uniweb/build": "~1.12.1"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -1155,7 +1155,7 @@ Four things you won't discover by reading exports:
 
 > **Content fields are HTML strings.** Covered above — it's the single most common rendering bug.
 
-> **`<Link>` takes `to` or `href`.** `to="page:about"` resolves a page ID (survives moves), external URLs get `target="_blank"` automatically, and `reload` forces a full page load.
+> **`<Link>` takes `to` or `href`.** `to="page:about"` resolves a page ID (survives moves) or a route, never a folder: the homepage is `page:/`, or `page:home` only when its `page.yml` says `id: home`. External URLs get `target="_blank"` automatically, and `reload` forces a full page load.
 
 > **`cn()` gotcha — a later `text-<size>` silently drops an earlier `leading-*`.** Tailwind's size classes set line height too, so `cn()` treats the size as replacing the leading: `cn('leading-[1.1] text-4xl')` → `text-4xl`. Put the size first, or fold the leading into it (`text-[clamp(2rem,5vw,4rem)]/[1.1]`). Most likely to bite when the size comes from a lookup and the leading sits in a shared base string.
 

package/src/backend/site-sync.js

@@ -2267,6 +2267,22 @@ export async function pushSyncPackages({
         // which is the case this message now names. Suggesting it there sends the
         // user to re-fetch a map they already have.
         if (problem.detail) note(String(problem.detail))
+        // ⭐ THE SITE'S FOLDER: one placement per record, keyed by the record it references, so
+        // its placements are all new when its records are — every record moved to another data
+        // schema, where a record keeps its type and each becomes a new one. The backend cannot
+        // tell that from identity lost, so it refuses, and the route is an empty folder first.
+        // ⛔ Until 2026-10-29 this said nothing more, and the type-change advice below led here:
+        // thirteen gallery records moving from @std/project to their foundation's own schema.
+        if (label === 'records' && where === 'contents') {
+          note(
+            "That section is the site's folder, one placement per record, and a placement is new when its " +
+              'record is — as when every record has moved to another data schema.'
+          )
+          note(
+            'To replace every record in the folder: push once with the records directory there and holding ' +
+              'nothing at all (the push asks, then removes them), then put the records back and push again.'
+          )
+        }
         return null
       }
       // ⭐ A RECORD KEEPS ITS TYPE. A record file moved to another type's folder keeps its `$uuid`, and
@@ -2279,6 +2295,13 @@ export async function pushSyncPackages({
           'A record keeps its type. To store it as the new type, make it a new record: delete the ' +
             '`$uuid` line from its file, then push again.'
         )
+        // ⚠️ Not the whole route when every record of the folder moves at once: each is then new,
+        // and so is every placement, which the folder refuses (`identity_required` above).
+        note(
+          'Moving every record in the folder to a new type? Then the folder refuses that push too: empty it ' +
+            'first — push once with the records directory there and holding nothing at all — then put the ' +
+            'records back without `$uuid` and push again.'
+        )
         return null
       }
       if (problem?.reason === 'stale_base') {

package/src/commands/publish.js

@@ -89,7 +89,7 @@ import {
   describeSyncedElsewhere
 } from '../utils/site-identity.js'
 import { isNonInteractive, confirm } from '../utils/interactive.js'
-import { guardEmptyRecords } from '../utils/records-guard.js'
+import { guardEmptyRecords, noteFolderLeftAlone } from '../utils/records-guard.js'
 import { findSiteCopies, describeSiteCopies } from '../utils/site-copies.js'
 import { headProvenance } from '../utils/git.js'
 import {
@@ -964,6 +964,8 @@ export async function publish(args = []) {
     return { exitCode: 1 }
   }
   for (const w of pkg.warnings) say.dim(`! ${w}`)
+  // A folder this publish leaves alone while the backend's still holds records — see `uniweb push`.
+  await noteFolderLeftAlone({ pkg, siteDir, backend: client.origin, note: (m) => say.dim(m) })
   if (refuseUnsendableRecords(pkg.refusals, { error: say.err, note: say.dim })) {
     return { exitCode: 1 }
   }

package/src/commands/push.js

@@ -79,7 +79,7 @@ import {
 } from '../utils/site-identity.js'
 import { confirm, isNonInteractive } from '../utils/interactive.js'
 import { announceServices, foundationSupports } from '../backend/service-request.js'
-import { guardEmptyRecords } from '../utils/records-guard.js'
+import { guardEmptyRecords, noteFolderLeftAlone } from '../utils/records-guard.js'
 import { bringFoundationAlong } from '../backend/foundation-bring-along.js'
 import { repoOf } from '../utils/sync-point.js'
 import {
@@ -627,6 +627,9 @@ export async function push(args = [], deps = {}) {
   const { siteContent, records, siteContentUuid, warnings, skipped } = pkg
   log('')
   for (const w of warnings) note(`! ${w}`)
+  // A folder this push leaves alone while the backend's still holds records — said, since an author
+  // who took the records out expects them gone (`noteFolderLeftAlone`).
+  await noteFolderLeftAlone({ pkg, siteDir, backend: client.origin, note })
   // The same stop for the paths the probe above does not run on — `-o` and
   // `--dry-run` say what a push would do, and a push would stop here.
   if (refuseUnsendableRecords(pkg.refusals, { error, note })) return { exitCode: 1 }

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-29T18:30:31.506Z",
+  "generatedAt": "2026-10-30T01:27:00.910Z",
   "packages": {
     "@uniweb/api": {
-      "version": "1.6.6"
+      "version": "1.6.7"
     },
     "@uniweb/build": {
-      "version": "1.11.4"
+      "version": "1.12.1"
     },
     "@uniweb/content-reader": {
       "version": "1.5.7"
@@ -15,16 +15,16 @@
       "version": "1.3.1"
     },
     "@uniweb/core": {
-      "version": "1.4.12"
+      "version": "1.5.0"
     },
     "@uniweb/frame-bridge": {
       "version": "1.0.2"
     },
     "@uniweb/icons": {
-      "version": "1.0.6"
+      "version": "1.0.7"
     },
     "@uniweb/kit": {
-      "version": "1.6.7"
+      "version": "1.6.8"
     },
     "@uniweb/loom": {
       "version": "1.1.2"
@@ -33,10 +33,10 @@
       "version": "1.1.4"
     },
     "@uniweb/projections": {
-      "version": "1.2.7"
+      "version": "1.2.8"
     },
     "@uniweb/runtime": {
-      "version": "1.2.13"
+      "version": "1.2.14"
     },
     "@uniweb/scene": {
       "version": "1.0.1"
@@ -60,7 +60,7 @@
       "version": "1.2.1"
     },
     "@uniweb/unipress": {
-      "version": "1.1.17"
+      "version": "1.1.18"
     }
   },
   "templates": {

package/src/utils/records-guard.js

@@ -86,3 +86,37 @@ export async function guardEmptyRecords({ siteDir, backend, args = [], warn, not
   const yes = await confirm(`Remove ${count} record${count === 1 ? '' : 's'} from the site's folder?`, false)
   return { ok: yes, count }
 }
+
+/**
+ * Say when a push leaves the backend's folder as it is although it holds records.
+ *
+ * A records directory that holds files but no records — data with no schema, say — states no
+ * folder, by design (`sendsFolder` in `@uniweb/build`): that is not an author emptying it. But an
+ * author who has just taken the records out and kept such files expects them gone from the
+ * backend, and the push said nothing (2026-10-29: a gallery's records moving to another schema,
+ * its schema-less articles left beside them). So where this copy holds placements from an earlier
+ * push or pull, say they stay, and how they would go.
+ *
+ * @param {object} params
+ * @param {object} params.pkg - what `emitSyncPackages` returned; `sendsFolder: false` is the case
+ * @param {string} params.siteDir
+ * @param {string} params.backend - whose placements to count
+ * @param {(m: string) => void} params.note - the caller's reporter
+ * @returns {Promise<number>} how many records the backend's folder keeps, as this copy last saw it
+ */
+export async function noteFolderLeftAlone({ pkg, siteDir, backend, note }) {
+  if (pkg?.sendsFolder !== false) return 0
+  const count = countPlacedRecords(readFolderItemUuids(siteDir, backend))
+  if (count === 0) return 0
+  const pool = await readEntityPool(siteDir)
+  const records = count === 1 ? '1 record' : `${count} records`
+  note(
+    `! The site's folder on the backend keeps its ${records}: this push leaves it as it is, because ` +
+      (pool.exists ? `${pool.dir}/ holds files but no records of a data schema.` : `there is no ${pool.dir}/ here.`)
+  )
+  note(
+    `  To remove ${count === 1 ? 'it' : 'them'} from the backend, push once with ${pool.dir}/ there and holding nothing at all ` +
+      `— the push asks first.`
+  )
+  return count
+}