uniweb 1.8.1 → 1.9.0

package/README.md

@@ -334,7 +334,7 @@ cd src
 uniweb register --scope @your-org
 ```
 
-Real sites built on your foundation are managed in the **Uniweb apps** (web + desktop) — visual editors designed for non-technical authors. They never see git, markdown, yaml, or React. They see *your* components, with live previews and visual controls for the params you defined. The foundation becomes the editor's native vocabulary for that site: you keep creative control of the design system, they get an editor that feels custom-built for them.
+Real sites built on your foundation are managed in the **Uniweb app** — a visual editor designed for non-technical authors. They never see git, markdown, yaml, or React. They see *your* components, with live previews and visual controls for the params you defined. The foundation becomes the editor's native vocabulary for that site: you keep creative control of the design system, they get an editor that feels custom-built for them.
 
 This is the best path when site content has a life independent of the foundation's release cycle — agencies, design studios, multi-client teams, or any project where content authors aren't the same people as the developers.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.8.1",
+  "version": "1.9.0",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/content-writer": "~1.1.2",
-    "@uniweb/core": "~1.2.2",
-    "@uniweb/semantic-parser": "~1.8.1",
-    "@uniweb/schemas": "~1.4.0"
+    "@uniweb/core": "~1.2.3",
+    "@uniweb/semantic-parser": "~1.9.0",
+    "@uniweb/schemas": "~1.4.0",
+    "@uniweb/content-writer": "~1.2.0"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.3.10",
-    "@uniweb/content-reader": "~1.4.0",
-    "@uniweb/semantic-parser": "~1.8.1"
+    "@uniweb/build": "~1.3.11",
+    "@uniweb/semantic-parser": "~1.9.0",
+    "@uniweb/content-reader": "~1.4.1"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -2796,8 +2796,6 @@ uniweb snapshot --compare         # Several looks on one sheet; take one with it
 uniweb <command> --help           # Per-command flags — no side effects. Prefer this over guessing.
 ```
 
-**Three verbs dispatch but are deliberately not listed above.** `invite`, `handoff` and `template` are **reserved names with no implementation** — the flows they named ran against a backend the CLI no longer talks to, and the names are held so a future rebuild doesn't need a breaking change. Running any of them is not useful; their absence from this list is the answer, not an omission to fix.
-
 ### Where a site can live
 
 **There is no lock-in, and no default you're pushed toward.** Four independent paths, and a project can change its mind:

package/src/backend/client.js

@@ -2,7 +2,7 @@
  * BackendClient — the single front door to the Uniweb backend.
  *
  * Every CLI verb that talks to the backend (register, push, pull, clone, org,
- * login — and, as the consolidation proceeds, publish/deploy/invite/handoff)
+ * login — and, as the consolidation proceeds, publish/deploy)
  * goes through one instance of this client instead of hand-rolling
  * `fetch(… Authorization: Bearer …)` against a per-command default origin. It
  * owns the three things that were previously scattered across a dozen files:

package/src/commands/pull.js

@@ -111,6 +111,7 @@ import {
   repoOf,
   mergeInProgress,
   unmergedPaths,
+  ignoringRepo,
   isAncestor,
   historySyncPoint,
   madeOnto,
@@ -485,8 +486,15 @@ async function checkWorkingTree(siteDir, args) {
   const roots = siteContentRoots(siteDir)
   const written = readWritten(siteDir)
   if (filesUnder(siteDir, roots).every((f) => isPullOutput(siteDir, f, written))) return null
+  // A folder the repository around it ignores is outside git too — said as such, since a
+  // repository is right there and "not in a repository" is not what the person sees.
+  const ignoredBy = ignoringRepo(siteDir)
   if (isNonInteractive(args)) {
-    error('Refusing to pull: this site is not in a git repository.')
+    error(
+      ignoredBy
+        ? 'Refusing to pull: this site is in a folder the repository around it ignores, so no repository holds it.'
+        : 'Refusing to pull: this site is not in a git repository.'
+    )
     note(
       'Pull rewrites pages, sections and layout from the backend and deletes what it no longer has.'
     )
@@ -494,12 +502,14 @@ async function checkWorkingTree(siteDir, args) {
       'Without version control there is no way back, and this session cannot ask.'
     )
     note(
-      'Re-run with --force to accept that, or put the site under git first — there a pull merges.'
+      ignoredBy
+        ? 'Re-run with --force to accept that, or give the site a repository of its own (`git init`, then commit) — there a pull merges.'
+        : 'Re-run with --force to accept that, or put the site under git first — there a pull merges.'
     )
     return { exitCode: 1 }
   }
   const ok = await confirm(
-    `Pull will overwrite ${roots.length} content location(s) and this site is not in git. Continue?`
+    `Pull will overwrite ${roots.length} content location(s), and no git repository holds this site. Continue?`
   )
   if (!ok) {
     info('Nothing pulled.')

package/src/commands/refresh.js

@@ -52,6 +52,7 @@ import {
   pullRemote,
   headProvenance
 } from '../utils/git.js'
+import { ignoringRepo } from '../utils/sync-point.js'
 import { probeUnpushed } from '../backend/site-sync.js'
 import { resolveBackendOrigin } from '../backend/client.js'
 import { readBackendState } from '@uniweb/build/uwx'
@@ -124,13 +125,18 @@ export async function refresh(args = [], deps = {}) {
   // when they are not.
   const consulted = []
   const skipped = []
+  // Said at the end — and before stopping on a failure, which can follow a step skipped.
+  const tell = () => {
+    if (consulted.length) say.dim(`Checked: ${consulted.join(', ')}`)
+    for (const s of skipped) say.dim(`Skipped: ${s}`)
+  }
   let conflicts = 0
 
   // ── 1. the git remote ─────────────────────────────────────────────────────
   if (skipGit) {
     skipped.push('git (--no-git)')
   } else if (!isGitRepo(siteDir)) {
-    skipped.push('git (not a repository)')
+    skipped.push(ignoringRepo(siteDir) ? 'git (the repository around this folder ignores it)' : 'git (not a repository)')
   } else if (!hasRemote(siteDir)) {
     skipped.push('git (no remote configured)')
   } else {
@@ -173,6 +179,7 @@ export async function refresh(args = [], deps = {}) {
       // Failed for a reason other than conflicts — say so plainly rather than
       // reporting a clean refresh over a lane that never ran.
       say.err('Could not merge the backend content.')
+      tell()
       return { exitCode: res.exitCode }
     }
     consulted.push('backend')
@@ -180,8 +187,7 @@ export async function refresh(args = [], deps = {}) {
 
   // ── 3. where that leaves you ──────────────────────────────────────────────
   console.log('')
-  if (consulted.length) say.dim(`Checked: ${consulted.join(', ')}`)
-  for (const s of skipped) say.dim(`Skipped: ${s}`)
+  tell()
 
   const git = headProvenance(siteDir)
   if (git)

package/src/framework-index.json

@@ -1,21 +1,21 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-17T22:35:38.030Z",
+  "generatedAt": "2026-10-18T05:12:16.689Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.5.0"
     },
     "@uniweb/build": {
-      "version": "1.3.10"
+      "version": "1.3.11"
     },
     "@uniweb/content-reader": {
-      "version": "1.4.0"
+      "version": "1.4.1"
     },
     "@uniweb/content-writer": {
-      "version": "1.1.2"
+      "version": "1.2.0"
     },
     "@uniweb/core": {
-      "version": "1.2.2"
+      "version": "1.2.3"
     },
     "@uniweb/frame-bridge": {
       "version": "1.0.2"
@@ -24,7 +24,7 @@
       "version": "1.0.3"
     },
     "@uniweb/kit": {
-      "version": "1.2.5"
+      "version": "1.3.0"
     },
     "@uniweb/loom": {
       "version": "1.1.0"
@@ -33,10 +33,10 @@
       "version": "1.1.1"
     },
     "@uniweb/projections": {
-      "version": "1.1.1"
+      "version": "1.1.2"
     },
     "@uniweb/runtime": {
-      "version": "1.1.4"
+      "version": "1.1.5"
     },
     "@uniweb/scene": {
       "version": "1.0.1"
@@ -48,7 +48,7 @@
       "version": "1.1.0"
     },
     "@uniweb/semantic-parser": {
-      "version": "1.8.1"
+      "version": "1.9.0"
     },
     "@uniweb/snapshot": {
       "version": "1.1.0"
@@ -60,7 +60,7 @@
       "version": "1.2.0"
     },
     "@uniweb/unipress": {
-      "version": "1.1.5"
+      "version": "1.1.6"
     }
   },
   "templates": {

package/src/index.js

@@ -33,8 +33,6 @@ import prompts from 'prompts'
 // Same pattern as `build` and `docs`.
 import { i18n } from './commands/i18n.js'
 import { inspect } from './commands/inspect.js'
-import { invite } from './commands/invite.js'
-import { handoff } from './commands/handoff.js'
 import { update } from './commands/update.js'
 import { clone } from './commands/clone.js'
 import { template } from './commands/template.js'
@@ -1010,18 +1008,6 @@ async function main() {
     return
   }
 
-  // Handle invite command
-  if (command === 'invite') {
-    await invite(args.slice(1))
-    return
-  }
-
-  // Handle handoff command
-  if (command === 'handoff') {
-    await handoff(args.slice(1))
-    return
-  }
-
   // Handle families command — the standard section families this CLI ships with
   if (command === 'families') {
     const { families } = await import('./commands/families.js')
@@ -1926,18 +1912,6 @@ Record files keep their \`$uuid\`: it is the record's own id, not a backend's.
 
 To duplicate a project:
   cp -r my-site my-site-2 && cd my-site-2 && uniweb forget --all
-`,
-    invite: `
-${colors.cyan}${colors.bright}uniweb invite${colors.reset} ${colors.dim}— (reserved; not available on the new backend yet)${colors.reset}
-
-The foundation client-invite flow was retired with the legacy backend.
-Invite clients to your foundation from the Uniweb app for now.
-`,
-    handoff: `
-${colors.cyan}${colors.bright}uniweb handoff${colors.reset} ${colors.dim}— (reserved; not available on the new backend yet)${colors.reset}
-
-The site-handoff flow was retired with the legacy backend.
-Manage client sites from the Uniweb app for now.
 `,
     families: `
 ${colors.cyan}${colors.bright}uniweb families${colors.reset} ${colors.dim}— The standard section families${colors.reset}

package/src/utils/install-integrity.js

@@ -14,9 +14,9 @@
  * foundation — `uniweb dev` with `foundation:` naming a sibling package. There,
  * the site imports `#foundation`, which `build/src/site/config.js` aliases to
  * the foundation's PACKAGE NAME, so Vite resolves it through node_modules. A
- * linked site (registry ref or URL) never takes that path, and neither does the
- * desktop app, unipress, or the edge — they load a built `dist/entry.js`, or
- * read a content folder directly. The check stays silent for all of them
+ * linked site (registry ref or URL) never takes that path, and neither does
+ * unipress or the edge — they load a built `dist/entry.js`, or read a content
+ * folder directly. The check stays silent for all of them
  * because there is no node_modules entry to look at.
  *
  * What goes wrong in that one modality: a `file:` dependency can be satisfied

package/src/utils/sync-point.js

@@ -107,6 +107,21 @@ export function repoOf(siteDir) {
   return { top, prefix, path: prefix ? prefix.replace(/\/$/, '') : '.', gitDir, head }
 }
 
+/**
+ * The top of the repository around `dir` when that repository ignores it — and so holds none
+ * of it — or null. For what is said to a person: "not in a repository" is not what they see
+ * when one is right there.
+ */
+export function ignoringRepo(dir) {
+  try {
+    const top = gitText(dir, ['rev-parse', '--show-toplevel']).trim()
+    const prefix = gitText(dir, ['rev-parse', '--show-prefix']).trim()
+    return top && prefix && ignoredHere(dir) ? top : null
+  } catch {
+    return null
+  }
+}
+
 /** Does the repository around `dir` ignore it? `git check-ignore` exits 0 for yes, 1 for no. */
 function ignoredHere(dir) {
   try {

package/src/commands/handoff.js

@@ -1,21 +0,0 @@
-/**
- * handoff — RESERVED (not available on the new backend yet).
- *
- * The "create a site and hand it off to a client" flow ran against the legacy
- * platform (the PHP backend + Cloudflare Worker) the CLI no longer talks to. A
- * new-backend CLI equivalent isn't built; the command name is kept reserved so a
- * future rebuild can claim it without a breaking change.
- */
-
-export async function handoff() {
-  console.error(
-    "\x1b[31m✗\x1b[0m `uniweb handoff` isn't available on the new backend yet."
-  )
-  console.error(
-    '  The legacy site-handoff flow was retired with the PHP backend.'
-  )
-  console.error('  Manage client sites from the Uniweb app for now.')
-  process.exit(1)
-}
-
-export default handoff

package/src/commands/invite.js

@@ -1,24 +0,0 @@
-/**
- * invite — RESERVED (not available on the new backend yet).
- *
- * The foundation client-invite flow ran against the legacy platform (the PHP
- * backend + Cloudflare Worker) the CLI no longer talks to. Client onboarding is
- * handled in the Uniweb app for now; a new-backend CLI equivalent isn't built.
- * The command name is kept reserved so a future rebuild can claim it without a
- * breaking change.
- */
-
-export async function invite() {
-  console.error(
-    "\x1b[31m✗\x1b[0m `uniweb invite` isn't available on the new backend yet."
-  )
-  console.error(
-    '  The legacy client-invite flow was retired with the PHP backend.'
-  )
-  console.error(
-    '  Invite clients to your foundation from the Uniweb app for now.'
-  )
-  process.exit(1)
-}
-
-export default invite