uniweb 0.12.26 → 0.12.27

package/src/commands/template.js

@@ -1,230 +1,22 @@
 /**
- * Template Command
+ * template — RESERVED (not available on the new backend yet).
  *
- * Publish a site as a cloud template.
+ * `uniweb template publish` submitted a site as a cloud template to the legacy
+ * registry (the PHP backend + Cloudflare Worker) the CLI no longer talks to. A
+ * new-backend equivalent isn't built; when it is, a template is REGISTERED (like
+ * a foundation or a schemas package) — the verb will be `register`, not `publish`
+ * (`publish` is for SITES only). The command name is kept reserved.
  *
- * Usage:
- *   uniweb template publish                  # Reads template name from site.yml `template:` field
- *   uniweb template publish --name my-tpl    # Override template name
- *   uniweb template publish --title "My Tpl" # Display title
- *   uniweb template publish --description "A starter template"
- *   uniweb template publish --registry <url> # Publish to a specific registry URL
+ * (Unrelated: scaffolding FROM a template — `uniweb create --template <name>` —
+ * is a separate path and is unaffected.)
  */
 
-import { existsSync } from 'node:fs'
-import { readFile, readdir } from 'node:fs/promises'
-import { resolve, join, relative } from 'node:path'
-import yaml from 'js-yaml'
-
-import { ensureAuth } from '../utils/auth.js'
-import { findWorkspaceRoot, findSites, classifyPackage } from '../utils/workspace.js'
-import { isNonInteractive, getCliPrefix } from '../utils/interactive.js'
-
-const colors = {
-  reset: '\x1b[0m',
-  bright: '\x1b[1m',
-  dim: '\x1b[2m',
-  cyan: '\x1b[36m',
-  green: '\x1b[32m',
-  yellow: '\x1b[33m',
-  red: '\x1b[31m',
-}
-
-function success(message) {
-  console.log(`${colors.green}✓${colors.reset} ${message}`)
-}
-
-function error(message) {
-  console.error(`${colors.red}✗${colors.reset} ${message}`)
-}
-
-function info(message) {
-  console.log(`${colors.cyan}→${colors.reset} ${message}`)
-}
-
-/**
- * Parse a named flag from args.
- * @param {string[]} args
- * @param {string} flag - e.g. '--name'
- * @returns {string|null}
- */
-function parseFlag(args, flag) {
-  const idx = args.indexOf(flag)
-  if (idx === -1 || !args[idx + 1]) return null
-  return args[idx + 1]
-}
-
-// Build infrastructure files to exclude from templates
-const EXCLUDED_FILES = new Set([
-  'package.json', 'package-lock.json', 'pnpm-lock.yaml',
-  'vite.config.js', 'vite.config.ts',
-  'index.html', 'main.js', 'main.ts',
-])
-const EXCLUDED_DIRS = new Set([
-  'node_modules', 'dist', '.git', '.vite',
-])
-
-/**
- * Resolve the site directory to publish as a template.
- *
- * Priority:
- * 1. In a site directory → use it
- * 2. site.yml in cwd (non-package site, e.g. cloud site) → use it
- * 3. At workspace root, one site → use it
- * 4. At workspace root, multiple → error
- * 5. No site → educational error
- */
-async function resolveSiteDir() {
-  const cwd = process.cwd()
-
-  // Check if current directory is a site package
-  const type = await classifyPackage(cwd)
-  if (type === 'site') return cwd
-
-  // Check for site.yml directly (non-package site, e.g. cloud site)
-  if (existsSync(join(cwd, 'site.yml'))) return cwd
-
-  // Check workspace
-  const workspaceRoot = findWorkspaceRoot(cwd)
-  if (workspaceRoot) {
-    const sites = await findSites(workspaceRoot)
-    if (sites.length === 1) return resolve(workspaceRoot, sites[0])
-    if (sites.length > 1) {
-      error('Multiple sites found. Run this command from inside the site directory.')
-      process.exit(1)
-    }
-  }
-
-  error('No site found. Run this command from a site directory (must contain site.yml).')
-  process.exit(1)
-}
-
-/**
- * Recursively read all files in a directory, returning { relativePath: base64Content }.
- * Skips build infrastructure files and directories.
- */
-async function readAllFiles(dir, baseDir = dir) {
-  const files = {}
-  const entries = await readdir(dir, { withFileTypes: true })
-
-  for (const entry of entries) {
-    const fullPath = join(dir, entry.name)
-    if (entry.isDirectory()) {
-      if (EXCLUDED_DIRS.has(entry.name)) continue
-      Object.assign(files, await readAllFiles(fullPath, baseDir))
-    } else if (entry.isFile()) {
-      if (EXCLUDED_FILES.has(entry.name)) continue
-      const relPath = relative(baseDir, fullPath)
-      const content = await readFile(fullPath)
-      files[relPath] = content.toString('base64')
-    }
-  }
-
-  return files
-}
-
-/**
- * Main template command dispatcher.
- */
-export async function template(args = []) {
-  const subcommand = args[0]
-
-  if (subcommand === 'publish') {
-    await templatePublish(args.slice(1))
-    return
-  }
-
-  const prefix = getCliPrefix()
-  error(subcommand ? `Unknown subcommand: template ${subcommand}` : 'Missing subcommand')
-  console.log('')
-  console.log(`${colors.bright}Usage:${colors.reset}`)
-  console.log(`  ${prefix} template publish    Publish a site as a cloud template`)
-  console.log('')
-  console.log(`${colors.bright}Options:${colors.reset}`)
-  console.log(`  --name <name>        Template registry name (overrides site.yml \`template:\` field)`)
-  console.log(`  --title <title>      Display title (overrides site.yml \`name:\` field)`)
-  console.log(`  --description <txt>  Description`)
-  console.log(`  --registry <url>     Registry URL (default: http://localhost:4001)`)
+export async function template() {
+  console.error("\x1b[31m✗\x1b[0m `uniweb template register` isn't available on the new backend yet.")
+  console.error('  Submitting a site as a cloud template was retired with the PHP backend.')
+  console.error('  A template is REGISTERED, like a foundation — `publish` is for sites only.')
+  console.error('  (Scaffolding FROM a template still works: `uniweb create --template <name>`.)')
   process.exit(1)
 }
 
-/**
- * Publish a site directory as a cloud template.
- */
-async function templatePublish(args) {
-  const registryUrl = parseFlag(args, '--registry')
-  const nameOverride = parseFlag(args, '--name')
-  const titleOverride = parseFlag(args, '--title')
-  const descOverride = parseFlag(args, '--description')
-
-  // 1. Resolve site directory
-  const siteDir = await resolveSiteDir()
-
-  // 2. Read and parse site.yml
-  const siteYmlPath = join(siteDir, 'site.yml')
-  if (!existsSync(siteYmlPath)) {
-    error('No site.yml found in this directory')
-    process.exit(1)
-  }
-
-  const siteYmlContent = await readFile(siteYmlPath, 'utf8')
-  const siteConfig = yaml.load(siteYmlContent) || {}
-
-  // 3. Determine template name: --name flag > site.yml `template:` field > directory name
-  const templateName = nameOverride || siteConfig.template || siteDir.split('/').pop()
-
-  if (!siteConfig.foundation) {
-    error('site.yml must declare a foundation')
-    process.exit(1)
-  }
-
-  // 4. Collect all content files (skip build infrastructure)
-  info(`Collecting files from ${colors.dim}${siteDir}${colors.reset}`)
-  const files = await readAllFiles(siteDir)
-  const fileCount = Object.keys(files).length
-
-  if (fileCount === 0) {
-    error('No files found to publish')
-    process.exit(1)
-  }
-
-  console.log(`  ${colors.dim}${fileCount} files${colors.reset}`)
-
-  // 5. Authenticate
-  const token = await ensureAuth({ command: 'Publishing template', args })
-
-  // 6. Build payload
-  const url = registryUrl || process.env.UNIWEB_REGISTRY_URL || 'http://localhost:4001'
-
-  const payload = { name: templateName, files }
-  if (titleOverride || siteConfig.name) {
-    payload.title = titleOverride || siteConfig.name
-  }
-  if (descOverride) payload.description = descOverride
-
-  // 7. Publish via API
-  info(`Publishing template ${colors.bright}${templateName}${colors.reset} to ${url}`)
-
-  const headers = { 'Content-Type': 'application/json' }
-  if (token) headers['Authorization'] = `Bearer ${token}`
-
-  const res = await fetch(`${url}/api/templates`, {
-    method: 'POST',
-    headers,
-    body: JSON.stringify(payload),
-  })
-
-  const body = await res.json()
-
-  if (!res.ok) {
-    error(body.error || `Server error (${res.status})`)
-    process.exit(1)
-  }
-
-  console.log('')
-  success(`Published template ${colors.bright}${templateName}${colors.reset}`)
-  console.log(`  ${colors.dim}Foundation: ${body.foundation}${colors.reset}`)
-  console.log(`  ${colors.dim}Files: ${body.filesCount}${colors.reset}`)
-}
-
 export default template

package/src/framework-index.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-06-12T00:10:21.149Z",
+  "generatedAt": "2026-06-15T03:29:50.221Z",
   "packages": {
     "@uniweb/build": {
-      "version": "0.14.10",
+      "version": "0.14.11",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -43,7 +43,7 @@
       "deps": []
     },
     "@uniweb/kit": {
-      "version": "0.9.15",
+      "version": "0.9.16",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -69,12 +69,12 @@
       ]
     },
     "@uniweb/scene": {
-      "version": "0.1.1",
+      "version": "0.1.2",
       "path": "framework/scene",
       "deps": []
     },
     "@uniweb/schemas": {
-      "version": "0.2.2",
+      "version": "0.2.3",
       "path": "framework/schemas",
       "deps": []
     },
@@ -99,7 +99,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.4.14",
+      "version": "0.4.15",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",
@@ -149,6 +149,17 @@
         "localization"
       ]
     },
+    "blog": {
+      "name": "Blog",
+      "description": "A blog built on the @std/article standard schema. Markdown articles render as a card grid and as full posts via dynamic [slug] routes. The first template to use a shared standard data schema — no custom schema file needed.",
+      "tags": [
+        "blog",
+        "articles",
+        "collections",
+        "standard-schema",
+        "data-schema"
+      ]
+    },
     "dynamic": {
       "name": "Dynamic Data",
       "description": "Live API data fetching with loading states, transforms, and the portable data pattern",

package/src/index.js

@@ -33,7 +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 { login } from './commands/login.js'
 import { invite } from './commands/invite.js'
 import { handoff } from './commands/handoff.js'
 import { update } from './commands/update.js'
@@ -134,7 +133,7 @@ function getCliVersion() {
 // install that's the whole point; delegating to the project-local copy
 // would align the project to the version it already has, i.e. a no-op.
 const STANDALONE_COMMANDS = new Set([
-  'create', 'clone', '--help', '-h', '--version', '-v', 'login', 'update',
+  'create', 'clone', '--help', '-h', '--version', '-v', 'login', 'logout', 'update',
 ])
 
 /**
@@ -664,11 +663,12 @@ async function main() {
     return
   }
 
-  // Handle publish command (dynamic import — depends on @uniweb/build)
+  // Handle publish command — CMS-publish a SYNCED site (POST /dev/site/publish).
+  // Distinct from `deploy` (file-built host) and `register` (foundation publishing).
   if (command === 'publish') {
     const { publish } = await importProjectCommand('./commands/publish.js')
-    await publish(args.slice(1))
-    return
+    const result = await publish(args.slice(1))
+    process.exit(result?.exitCode ?? 0)
   }
 
   // Handle deploy command (dynamic import — depends on @uniweb/build)
@@ -692,18 +692,27 @@ async function main() {
     return
   }
 
-  // Handle login command. Default targets the NEW backend (username/password);
-  // `--legacy` runs the old browser/social flow (still used by publish/deploy
-  // internally via ensureAuth, so it stays reachable).
+  // Handle login command — the backend (username/password · paste a token ·
+  // --token <bearer>). Origin from --backend/--registry > UNIWEB_REGISTER_URL >
+  // default, the SAME resolver register/push/pull/deploy use, so a session and
+  // the commands that reuse it always target one backend.
   if (command === 'login') {
     const loginArgs = args.slice(1)
-    if (loginArgs.includes('--legacy')) {
-      await login(loginArgs.filter((a) => a !== '--legacy'))
-    } else {
-      const { getRegistryApiBaseUrl } = await import('./utils/config.js')
-      const { runRegistryLogin } = await import('./utils/registry-auth.js')
-      await runRegistryLogin({ apiBase: getRegistryApiBaseUrl(), args: loginArgs })
-    }
+    const { resolveBackendOrigin } = await import('./backend/client.js')
+    const { readFlagValue } = await import('./utils/args.js')
+    const { runRegistryLogin } = await import('./utils/registry-auth.js')
+    const originFlag = readFlagValue(loginArgs, '--backend') || readFlagValue(loginArgs, '--registry')
+    await runRegistryLogin({ apiBase: resolveBackendOrigin(originFlag), args: loginArgs })
+    return
+  }
+
+  // Handle logout command — clear the stored backend session.
+  if (command === 'logout') {
+    const { clearRegistryAuth, getRegistryAuthPath } = await import('./utils/registry-auth.js')
+    const { existsSync } = await import('node:fs')
+    const had = existsSync(getRegistryAuthPath())
+    await clearRegistryAuth()
+    console.log(had ? '\x1b[32m✓\x1b[0m Logged out (cleared the stored session).' : 'Not logged in — nothing to clear.')
     return
   }
 
@@ -714,6 +723,14 @@ async function main() {
     return
   }
 
+  // Handle runtime command — `runtime register` uploads a built @uniweb/runtime to
+  // the backend's runtime registry (/gateway/runtime/{version}); @std-gated.
+  if (command === 'runtime') {
+    const { runtime } = await import('./commands/runtime.js')
+    const result = await runtime(args.slice(1))
+    process.exit(result?.exitCode ?? 0)
+  }
+
   // Handle invite command
   if (command === 'invite') {
     await invite(args.slice(1))
@@ -1105,24 +1122,20 @@ ${colors.bright}Examples:${colors.reset}
   uniweb deploy --target=preview             # Pick named target from deploy.yml
 `,
     publish: `
-${colors.cyan}${colors.bright}uniweb publish${colors.reset} ${colors.dim}— Publish a foundation to the catalog${colors.reset}
+${colors.cyan}${colors.bright}uniweb publish${colors.reset} ${colors.dim}— Publish a synced site (make its backend state live)${colors.reset}
 
 ${colors.bright}Usage:${colors.reset}
-  uniweb publish [@org/name] [options]
+  uniweb publish [options]
 
-For site-bound foundations (one foundation, one site), use \`uniweb deploy\`
-instead — it auto-publishes under a site-scoped slot, no naming ceremony.
+Publishes a site that's synced to the backend (has site.yml::\$uuid from
+\`uniweb push\`) — makes its CURRENT backend state live, including edits made
+through the app. Run \`uniweb push\` first to include local edits. For a
+file-only site use \`uniweb deploy\`; to register a FOUNDATION use \`uniweb register\`.
 
 ${colors.bright}Options:${colors.reset}
-  --catalog          Confirm publish to the public catalog (required in CI)
-  --propagate        Walk trusting sites' policy waves (default: silent)
-  --name <id>        Foundation id (overrides package.json::uniweb.id)
-  --namespace <ns>   Force org-scope namespace (overrides package.json)
-  --local            Internal: publish to the unicloud mock (see workspace root CLAUDE.md)
-  --registry <url>   Use a specific registry URL
-  --edit-access <p>  "open" or "restricted" (default: restricted)
-  --dry-run          Show what would be published without uploading
-  --non-interactive  Fail with usage info instead of prompting
+  --backend <url>    Backend origin (default: \$UNIWEB_REGISTER_URL or built-in)
+  --token <bearer>   Auth bearer (skips \`uniweb login\`)
+  --dry-run          Resolve everything; POST nothing
 `,
     create: `
 ${colors.cyan}${colors.bright}uniweb create${colors.reset} ${colors.dim}— Create a new project${colors.reset}
@@ -1262,8 +1275,9 @@ ${colors.bright}Usage:${colors.reset}
   uniweb register [options]
 
 Builds one \`.uwx\` document and submits it to the registry over HTTP. Run
-\`uniweb login\` first (or pass \`--token\`). Distinct from \`uniweb publish\` (legacy
-hosting platform).
+\`uniweb login\` first (or pass \`--token\`). \`register\` is for FOUNDATIONS (and
+schemas); \`uniweb publish\` makes a synced SITE live; \`uniweb deploy\` hosts a
+file-built site.
 
 Auto-detects what you run it in:
   • a foundation        the foundation + the data schemas it defines/renders
@@ -1321,52 +1335,38 @@ ${colors.cyan}${colors.bright}uniweb login${colors.reset} ${colors.dim}— Log i
 ${colors.bright}Usage:${colors.reset}
   uniweb login [options]
 
-Opens a browser to www.uniweb.app for OAuth-style login, then captures
-the token via a loopback callback. Falls back to a paste-token prompt
-if the browser flow fails.
+Authenticates with the backend and stores a session at
+~/.uniweb/registry-auth.json. Every backend command (register, push, pull,
+clone, deploy) reuses it. Interactively, pick username/password or paste a token.
 
 ${colors.bright}Options:${colors.reset}
-  --backend <url>    Override the auth backend (default: https://www.uniweb.app)
-
-In non-interactive mode (CI / no TTY / --non-interactive), this command
-errors out — set the \`UNIWEB_TOKEN\` env var instead, or run \`login\`
-once on a machine with a browser to seed ~/.uniweb/auth.json.
+  --backend <url>    Backend origin (default: \$UNIWEB_REGISTER_URL or built-in)
+  --token <bearer>   Seed + verify a session from a bearer token (non-interactive)
+  --password         Force the username/password method
+  --token-paste      Force the paste-a-token prompt
+
+In non-interactive mode (CI / no TTY), pass \`--token <bearer>\`, or set
+\`UNIWEB_USERNAME\` + \`UNIWEB_PASSWORD\`, or set \`UNIWEB_TOKEN\` (used per-command,
+not stored). Run \`uniweb logout\` to clear the stored session.
 `,
     invite: `
-${colors.cyan}${colors.bright}uniweb invite${colors.reset} ${colors.dim}— Create a foundation invite for a client${colors.reset}
-
-${colors.bright}Usage:${colors.reset}
-  uniweb invite <email> [options]
+${colors.cyan}${colors.bright}uniweb invite${colors.reset} ${colors.dim}— (reserved; not available on the new backend yet)${colors.reset}
 
-${colors.bright}Options:${colors.reset}
-  --uses <n>         Max sites per invite (default: 1)
-  --expires <days>   Days until expiry (default: 30)
-  --version <n>      Major version to license (default: current)
-  --list             List invites for your foundation
-  --revoke <id>      Revoke an invite
-  --resend <id>      Resend an invite
+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}— Hand off a site to a client${colors.reset}
-
-${colors.bright}Usage:${colors.reset}
-  uniweb handoff <email> [options]
+${colors.cyan}${colors.bright}uniweb handoff${colors.reset} ${colors.dim}— (reserved; not available on the new backend yet)${colors.reset}
 
-${colors.bright}Options:${colors.reset}
-  --site <id>        Site identifier (default: auto-generated)
-  --web              Show web-based handoff instructions instead
+The site-handoff flow was retired with the legacy backend.
+Manage client sites from the Uniweb app for now.
 `,
     template: `
-${colors.cyan}${colors.bright}uniweb template${colors.reset} ${colors.dim}— Manage cloud templates${colors.reset}
-
-${colors.bright}Subcommands:${colors.reset}
-  template publish        Publish a site as a cloud template
+${colors.cyan}${colors.bright}uniweb template${colors.reset} ${colors.dim}— (reserved; not available on the new backend yet)${colors.reset}
 
-${colors.bright}Publish Options:${colors.reset}
-  --name <name>      Template registry name (overrides site.yml template: field)
-  --title <title>    Display title (overrides site.yml name: field)
-  --description <t>  Description
-  --registry <url>   Registry URL (default: http://localhost:4001)
+Submitting a site as a cloud template was retired with the legacy backend.
+When rebuilt, a template is REGISTERED (like a foundation) — \`publish\` is for
+sites only. Scaffolding FROM a template still works: \`uniweb create --template <name>\`.
 `,
     docs: `
 ${colors.cyan}${colors.bright}uniweb docs${colors.reset} ${colors.dim}— Generate component documentation${colors.reset}
@@ -1465,20 +1465,19 @@ ${colors.bright}Commands:${colors.reset}
   build              Build the current project
   deploy             Deploy a site to Uniweb hosting
   export             Export a self-contained site for third-party hosting
-  publish            Publish a foundation to the Uniweb registry
+  publish            Publish a synced site (make its backend state live)
   register           Register a foundation + its data schemas with the backend registry
+  runtime register   Register an @uniweb/runtime version to the backend (@std only)
   push               Push a site's content to the backend
   pull               Pull a site's content from the backend
-  invite <email>     Create a foundation invite for a client
-  handoff <email>    Hand off a site to a client
   inspect <path>     Inspect parsed content shape of a markdown file or folder
   docs               Generate component documentation
   doctor             Diagnose project configuration issues
   validate           Check your content against your foundation's data schemas
   update             Align workspace deps + AGENTS.md to the running CLI
   i18n <cmd>         Internationalization (extract, sync, status)
-  template publish   Publish a site as a cloud template
   login              Log in to your Uniweb account
+  logout             Clear the stored session
 
 ${colors.bright}Create Options:${colors.reset}
   --template <type>  Project template (default: starter)
@@ -1499,37 +1498,12 @@ ${colors.bright}Global Options:${colors.reset}
                        Auto-detected when CI=true or no TTY (pipes, agents)
 
 ${colors.bright}Publish Options:${colors.reset}
-  --catalog          Confirm publish to the public catalog (required in CI)
-  --propagate        Walk trusting sites' policy waves (default: silent)
-  --name <id>        Foundation id (overrides package.json::uniweb.id)
-  --namespace <ns>   Force org-scope namespace (overrides package.json)
-  --local            Publish to the local registry (.unicloud/) instead of Uniweb Registry
-  --registry <url>   Use a specific registry URL
-  --edit-access <p>  Set edit access policy: "open" or "restricted" (default: restricted)
-  --dry-run          Show what would be published without uploading
-
-  uniweb publish is for cataloging a foundation as a product. For
-  site-bound foundations (one foundation, one site), use uniweb deploy
-  instead — it auto-publishes under a site-scoped slot, no naming
-  ceremony.
-
-${colors.bright}Invite Options:${colors.reset}
-  --uses <n>         Max sites per invite (default: 1)
-  --expires <days>   Days until expiry (default: 30)
-  --version <n>      Major version to license (default: current)
-  --list             List invites for your foundation
-  --revoke <id>      Revoke an invite
-  --resend <id>      Resend an invite
-
-${colors.bright}Handoff Options:${colors.reset}
-  --site <id>        Site identifier (default: auto-generated)
-  --web              Show web-based handoff instructions instead
-
-${colors.bright}Template Options:${colors.reset}
-  --name <name>      Template registry name (overrides site.yml template: field)
-  --title <title>    Display title (overrides site.yml name: field)
-  --description <t>  Description
-  --registry <url>   Registry URL (default: http://localhost:4001)
+  --backend <url>    Backend origin (default: \$UNIWEB_REGISTER_URL or built-in)
+  --token <bearer>   Auth bearer (skips \`uniweb login\`)
+  --dry-run          Resolve everything; POST nothing
+
+  uniweb publish makes a SYNCED site live (run \`uniweb push\` first). To register
+  a foundation use \`uniweb register\`; to host a file-built site use \`uniweb deploy\`.
 
 ${colors.bright}Deploy Options:${colors.reset}
   --target <name>    Pick a target from deploy.yml (default: deploy.yml's \`default:\`)