@xano/sdk 1.0.4 → 1.0.6

package/guides/bundle.md

@@ -0,0 +1,45 @@
+# Reading a compiled bundle
+
+`@xano/sdk` writes a bundle; `@xano/sdk/bundle` reads one back. It is the surface for
+tools that take compiled JSON as input — a graph view, a diff, a linter, a docs generator —
+so none of them has to reverse-engineer the storage shape and then go quietly wrong when the
+engine grows a new one.
+
+A bundle is what `export` writes:
+
+```bash
+npx xanosdk export ./xano/index.ts --out workspace.json
+```
+
+```ts
+import { readFile } from "node:fs/promises";
+import { statementCatalog, walk } from "@xano/sdk/bundle";
+
+const bundle = JSON.parse(await readFile("bundle.json", "utf8"));
+const catalog = statementCatalog();
+
+for (const { raw, path, depth } of walk(bundle.payload.query[0].run)) {
+  console.log(`${"  ".repeat(depth)}${path}  ${catalog.get(raw.name)?.sPath ?? raw.name}`);
+}
+// 0       db.query
+// 1       conditional
+// 1.if.0  db.add
+```
+
+- **`walk(run)`** → every statement in the tree, each with a `path` and a `depth`. The path
+  format (`2.if.0`) is the shared address: a lint finding, a review comment and a runtime
+  error written by three different tools all name the same node.
+- **`subStacks(raw)`** → the nested stacks a statement carries, keyed by where they are
+  stored and labelled by what they mean — a try/catch and a conditional share the same three
+  storage keys. Found by shape, so a nesting form added later is still walked.
+- **`statementCatalog()`** → the stored `mvp:*` name to its authoring path, minus the
+  namespace (`mvp:dbo_view` → `db.query`, the `sPath` you write after `s.`) — which is
+  the point: the stored name is often not the one you'd guess.
+- **`structuralHash(raw)`** → a diff key for a statement and everything under it, with
+  engine-filled operands excluded — so adding a column to a table leaves `db.edit` /
+  `db.add_or_edit` unchanged. A `db.add` writes every column, so its hash does change.
+- **`tableRefOf(column)` / `linkedTableOf(column)`** → the table a column points at.
+- **`normalize(value)`** → the normalizer `xanosdk preflight` compares with, for diffing a
+  stored workspace against a compiled one.
+
+Everything on the entry is pure — no filesystem, network, or Node built-ins — so it runs anywhere.

package/guides/cli.md

@@ -41,44 +41,46 @@ xanosdk login --scope "<list>"              # request these OAuth scopes instead
 xanosdk login --profile staging             # sign in as a second named credential, leaving the others alone
 xanosdk <command> --profile staging         # act as that profile for one run (-p is the short form)
 xanosdk workspace details                   # which instance/workspace am I bound to, and via which credential?
-xanosdk deploy ./xano/index.ts              # compile + import into a live ephemeral (the dev loop) → URL
-xanosdk deploy ./xano/index.ts --static ./frontend/dist   # also deploy a static frontend (onto the ephemeral)
-xanosdk deploy ./xano/index.ts --static ./frontend/dist --static-env PK=pk_live_1   # + extra public config
+xanosdk deploy ./xano/index.ts              # compile + import into the Xano Engine on this machine (the dev loop) → URL; no account needed
+xanosdk deploy ./xano/index.ts --ephemeral  # …or into a live ephemeral on Xano's cloud → URL
+xanosdk deploy ./xano/index.ts --ephemeral --static ./frontend/dist   # also deploy a static frontend (onto the ephemeral)
+xanosdk deploy ./xano/index.ts --ephemeral --static ./frontend/dist --static-env PK=pk_live_1   # + extra public config
 xanosdk deploy --bundle ws.json             # deploy an already-exported bundle
 xanosdk deploy ./xano/index.ts --open       # …and open the deployed URL in your browser
-xanosdk deploy ./xano/index.ts --expires-hours 8   # the ephemeral's TTL when this deploy creates it: 1–24 hours (default: 1)
-xanosdk deploy ./xano/index.ts --keep-data --static ./frontend/dist --static-host docs   # publish to a named static host — merge only: a replace deletes it, and a deploy creates only `default` (create `docs` in the dashboard first)
-xanosdk deploy ./xano/index.ts --static ./frontend/dist --static-routing spa   # override URL resolution, spa|multipage (inferred from the bundle; rarely needed)
+xanosdk deploy ./xano/index.ts --ephemeral --expires-hours 8   # the ephemeral's TTL when this deploy creates it: 1–24 hours (default: 1)
+xanosdk deploy ./xano/index.ts --ephemeral --keep-data --static ./frontend/dist --static-host docs   # publish to a named static host — merge only: a replace deletes it, and a deploy creates only `default` (create `docs` in the dashboard first)
+xanosdk deploy ./xano/index.ts --ephemeral --static ./frontend/dist --static-routing spa   # override URL resolution, spa|multipage (inferred from the bundle; rarely needed)
 xanosdk deploy ./xano/index.ts --keep-data  # redeploy but keep table rows (merge instead of replace; seeds aren't re-written)
 xanosdk env set STRIPE_KEY --to workspace --yes   # set ONE env var on a running backend, value piped on stdin (no deploy; never printed)
-xanosdk env unset STRIPE_KEY --to local-engine # clear one (--to workspace|ephemeral[:<name>]|local-engine[:<name>]|tenant:<name>, default: last deployed)
+xanosdk env unset STRIPE_KEY --to local # clear one (--to workspace|ephemeral[:<name>]|local[:<name>]|tenant:<name>, default: last deployed)
 xanosdk publish ./frontend/dist             # publish a built frontend alone — no compile, no backend import (default: last deployed)
-xanosdk publish ./frontend/dist --to ephemeral   # …after a local-engine deploy: publish does not reach a local engine
-xanosdk deploy ./xano/index.ts --local-engine --static ./frontend/dist   # the engine serves the build at http://<prefix>.localhost:<port>
+xanosdk publish ./frontend/dist --to ephemeral   # …or onto an ephemeral instead (after a local deploy, bare publish goes to the engine)
+xanosdk deploy ./xano/index.ts --static ./frontend/dist   # on the Xano Engine, the engine serves the build at http://<prefix>.localhost:<port>
 xanosdk publish ./frontend/dist --to workspace --branch v2 --yes   # …onto the workspace, refused unless branch v2 is live
-xanosdk deploy ./xano/index.ts --local-engine   # deploy to a local engine on this machine instead of an ephemeral (runs the version pinned in package.json)
-xanosdk deploy ./xano/index.ts --local-engine=~/Downloads/engine.tar.gz   # override: run this archive, URL or version (v0.1.8), never touching the pin
-XANOSDK_LOCAL_ENGINE_OVERRIDE=v0.1.8 npm run xano:deploy:local-engine   # the same override for every deploy in the shell
-xanosdk local-engine list                   # local engines on this machine, marking the ones xanosdk started
-xanosdk local-engine token                  # print its meta API bearer: XANO_META_TOKEN=$(xanosdk local-engine token)
-xanosdk local-engine stop <name>            # stop one (--all: every one xanosdk started, and what a crashed one left running)
-xanosdk local-engine update                 # move this project's pinned engine to the latest (--version <v>: that one) and restart it — commit package.json
-xanosdk local-engine cache list             # each cached engine version, its size, and the engines running on it
-xanosdk local-engine cache clear            # remove every cached engine and its unpacked runtime (--version <v>: just that one); running ones are stopped first
+xanosdk deploy ./xano/index.ts --local   # the default, spelled out: the Xano Engine on this machine (runs the version pinned in package.json)
+xanosdk deploy ./xano/index.ts --local=~/Downloads/engine.tar.gz   # override: run this archive, URL or version (v0.1.8), never touching the pin
+XANOSDK_ENGINE_OVERRIDE=v0.1.8 npm run xano:deploy   # the same override for every deploy in the shell
+xanosdk local list                   # Xano Engines on this machine, marking the ones xanosdk started
+xanosdk local token                  # print its meta API bearer: XANO_META_TOKEN=$(xanosdk local token)
+xanosdk local stop <name>            # stop one (--all: every one xanosdk started, and what a crashed one left running)
+xanosdk local update                 # move this project's pinned engine to the latest (--version <v>: that one) and restart it — commit package.json
+xanosdk local cache list             # each cached engine version, its size, and the engines running on it
+xanosdk local cache clear            # remove every cached engine and its unpacked runtime (--version <v>: just that one); running ones are stopped first
 xanosdk ephemeral list                      # list your ephemeral environments (--all-workspaces spans every workspace; --json: { ephemerals: [...] })
 xanosdk ephemeral get <name>                # base URL, state, and expiry for one (<name> = the tenant name, e.g. ewap-8wz9-9e13, NOT the display name — `ephemeral list` shows it in bold)
 xanosdk ephemeral delete <name> --yes       # destroy one
 xanosdk tables                              # the last-deployed backend's tables: id, guid, name (for release create --seed)
 xanosdk tables tenant:acme                  # …or name one
 xanosdk test run-all                        # run the tests the last-deployed backend carries (exits 5 on a failure)
-xanosdk test run-all --on local-engine      # …or name one (--on ephemeral:<name>|tenant:<name>|workspace)
+xanosdk test run-all --on local      # …or name one (--on ephemeral:<name>|tenant:<name>|workspace)
 xanosdk test list                           # list the tests a backend carries, without running any
+xanosdk test run "<name>"                   # run one test by its name
 xanosdk test run-all --kind unit            # only one family (unit|workflow; default: both) — also on test list
 xanosdk test run-all --concurrency 4        # run 4 at once (default: 1); tests share the backend's database, so only when yours don't share state
 xanosdk impersonate                         # open what this project last deployed to in the builder (--guest = read-only; --url-only prints the URL; the URL is a session — treat it as a credential)
-xanosdk impersonate ephemeral:<tenant>      # …or name one: local-engine[:<name>] or tenant:<name> (open your workspace from the Xano dashboard)
+xanosdk impersonate ephemeral:<tenant>      # …or name one: local[:<name>] or tenant:<name> (open your workspace from the Xano dashboard)
 xanosdk deploy ./xano/index.ts --test        # THE RELEASE FLOW, step 1: stand it up and run its tests
-xanosdk release create v1                   # …2: cut a release from the ephemeral this project last deployed to (after a local-engine deploy: --from ephemeral)
+xanosdk release create v1                   # …2: cut a release from the ephemeral this project last deployed to (after a local deploy: --from ephemeral)
 xanosdk release create v1 --from ephemeral:e4f2-9ab1 --description "what shipped"   # …from a named source
 xanosdk release create v1 --from workspace --branch staging   # …or from a branch of your workspace (default: what it serves)
 xanosdk release list                        # every release in this workspace, newest first, a description cut to one line (--json: { releases: [...] }, each with the origin show names)
@@ -94,7 +96,7 @@ xanosdk tenant list                         # every tenant under this workspace
 xanosdk tenant get acme                     # base URL and state for one
 xanosdk tenant deploy acme v1               # …or 3: land it on a customer tenant instead
 xanosdk tenant delete acme --yes            # destroy one (by its NAME — a display name fails with exit 8 and names the tenant it belongs to)
-xanosdk pull release:v1                     # refresh xano/ from a release: rewrites decoded files, keeps and names files you added, lists and confirms (also workspace, ephemeral[:<name>], local-engine, tenant:<name>)
+xanosdk pull release:v1                     # refresh xano/ from a release: rewrites decoded files, keeps and names files you added, lists and confirms (also workspace, ephemeral[:<name>], local, tenant:<name>)
 xanosdk pull release:v1 --yes               # …skip the confirmation and the dirty-tree refusal (CI)
 xanosdk pull workspace --backend-dir ./backend   # …when this project keeps its backend somewhere other than xano/ and nothing on disk says so (also on env pull)
 xanosdk generate release:v1 --out ./backend # write ONLY the decoded xano/ tree, no project around it (any source above, or a bundle path; --force replaces the files an earlier generate wrote, asks first when that loses your edits (--yes answers), and keeps and lists any others)
@@ -110,7 +112,7 @@ xanosdk ephemeral export <name> --format multidoc --path -          # …stream
 
 xanosdk workspace details                   # which workspace your token is scoped to (instance, id, name)
 xanosdk workspace export --path ws.json     # your REAL workspace as a JSON bundle (`--path -` streams to stdout)
-xanosdk workspace diff ./xano/index.ts --branch staging   # did my release land? which objects on the branch differ from your compile, are missing, or are unexpected (default: live); exits 2 when anything declared differs or is missing
+xanosdk workspace diff ./xano/index.ts --branch staging   # did my release land? which objects on the branch differ from your compile, are missing, or are unexpected (default: live), and which side changed each since the last sync (`changedThere`/`changedHere`/`changedBoth`); exits 2 when anything declared differs or is missing
 xanosdk workspace branch list               # its branches, and which one is live
 xanosdk workspace branch set-live staging   # promote a branch (also the way back after --backup-branch)
 xanosdk workspace branch delete staging --yes   # remove a non-live branch (a label padded with spaces is found by the trimmed one; one not there exits 0, alreadyGone; the live branch exits 2, SDK_BRANCH_LIVE)
@@ -135,7 +137,7 @@ xanosdk help                                # grouped command reference (also th
 xanosdk <command> --help                    # that command's usage, subcommands, and flags (`xanosdk deploy --help`)
 xanosdk <noun> <verb> --help                # scoped to one verb (`xanosdk workspace export --help`)
 xanosdk <command> --json                    # force JSON on stdout (otherwise: whenever stdout isn't a terminal)
-xanosdk <command> --no-refresh              # don't refresh the managed block in AGENTS.md (a build that writes nothing outside its output)
+xanosdk <command> --no-refresh              # don't refresh the managed blocks in AGENTS.md and the README (a build that writes nothing outside its output)
 xanosdk completion zsh                      # shell completion script (also bash, fish) — see below
 
 xanosdk preflight ./xano/index.ts           # import into a live instance, diff each object back (needs auth + a throwaway tenant)
@@ -155,7 +157,7 @@ Every command that reads, writes or opens a running backend names it with one gr
 |---|---|
 | `workspace` | Your real workspace — the one your login is scoped to |
 | `ephemeral` / `ephemeral:<name>` | The ephemeral this project deployed to, or a named one — by its name (`e4f2-9ab1`, from `xanosdk ephemeral list`), not its display name |
-| `local-engine` / `local-engine:<name>` | The engine this project deployed to, or a named one from `xanosdk local-engine list`. Needs no Xano account |
+| `local` / `local:<name>` | The engine this project deployed to, or a named one from `xanosdk local list`. Needs no Xano account |
 | `tenant:<name>` | A tenant on your instance |
 | `release:<name>` | A stored release — where a command reads one (`deploy`, `pull`, `generate`, `init --from`) |
 | a bundle path | Where a command takes a file (`deploy`, `generate`, `init --from`) |
@@ -166,20 +168,20 @@ takes **`--on`**, and a command whose subject IS the backend takes it positional
 `pull`, `generate`, `tables`, `impersonate`).
 
 **Leave it off and a command follows the backend this project last deployed to** — recorded
-in `.xano/deployed.json` by an ephemeral or local-engine deploy, and never by a deploy to your
+in `.xano/deployed.json` by an ephemeral or local deploy, and never by a deploy to your
 workspace or a tenant, so a bare command cannot reach something real unasked. With no record,
 it falls back to the ephemeral recorded under your current credential, then to the engine
 recorded for this directory, and otherwise refuses naming the flag, `xanosdk deploy` and
-`xanosdk deploy --local-engine`.
+`xanosdk deploy --local`.
 `deploy` is the exception: bare, it compiles the project and stands it up on an ephemeral
-unless `--to` or `--local-engine` says otherwise, so it writes that record rather than
+unless `--to` or `--local` says otherwise, so it writes that record rather than
 reading it. `generate` and `init --from` need a backend named.
 
 A command that cannot serve a backend refuses it, whether you typed it or it came from the
-record, with the reason and the spellings it does take: `publish` refuses a local engine (no
+record, with the reason and the spellings it does take: `publish` refuses a Xano Engine (no
 static host — pass `--to ephemeral`), and so does `release create` (the cut runs on the
 instance — pass `--from ephemeral`). A write to your workspace or a tenant confirms first,
-or needs `--yes` off a terminal; an ephemeral or local engine never asks.
+or needs `--yes` off a terminal; an ephemeral or Xano Engine never asks.
 
 ## Bundle key names vs. the names everything else uses
 
@@ -253,7 +255,7 @@ layer raised it — is `SDK_EXPORT_INVALID`, with its checks in `error.details.d
 `destination`, a read's `kind`/`name` (`tables`, `test`), `status`, `ephemeral get`,
 `workspace details`, `impersonate`, and each `tenant list`/`ephemeral list` row — also carries
 `selector`, the spelling the next command's backend slot takes (`"ephemeral:e4f2-9ab1"`,
-`"tenant:acme"`, `"local-engine:<name>"`, `"workspace"`; `ephemeral get|delete|export` and
+`"tenant:acme"`, `"local:<name>"`, `"workspace"`; `ephemeral get|delete|export` and
 `tenant get|deploy|delete` take it as well as the bare name), and `workspaceId`, the numeric workspace it acts on (for an ephemeral or tenant,
 the workspace it lives under). The fields each command already had stay. `export --out --json`
 carries `written: true`, as `export --check` carries `written: false`. `help --json` lists each
@@ -264,7 +266,7 @@ string, `values` its whole closed set, `examples` a few values of a flag that ta
 ## Shell completion
 
 `xanosdk completion <bash|zsh|fish>` prints a completion script covering every command, verb, flag,
-and closed value set (`--on workspace|ephemeral|local-engine`, `--format json|multidoc`, `--icons lucide|tabler|phosphor`).
+and closed value set (`--on workspace|ephemeral|local`, `--format json|multidoc`, `--icons lucide|tabler|phosphor`).
 A flag's value completes as what it takes: its closed set, file names for a path (`--config`,
 `--secrets-file`), directories for a directory (`--backend-dir`), stored profile names for
 `--profile`/`--to-profile`, and nothing for a free-form value (`--name`, `--expires-hours`).
@@ -312,8 +314,8 @@ as `installed`. The install matches how this CLI is installed (`npm i -g` for a
 project, `--save-prod` when `@xano/sdk` is in `dependencies`, as a scaffold puts it, else
 `--save-dev`) — and for a project-local install it
 then restores the `@xano/sdk` range your project was scaffolded with (npm rewrites it to a
-caret) and restamps the managed block in your
-agent files so the guidance matches the version you now have. Set `XANOSDK_INSTALL_MODE` to
+caret) and restamps the managed blocks in your
+`AGENTS.md` and README so what they say matches the version you now have. Set `XANOSDK_INSTALL_MODE` to
 `global` or `local` to override the detection. Run through `npx` (or `pnpm dlx`, `yarn dlx`, `bunx`)
 outside a project, it installs nothing (`status: "not-installed"`): that copy is temporary,
 and `npx @xano/sdk@latest` already runs the newest release.

package/guides/codegen.md

@@ -10,12 +10,12 @@ so it is the scaffold command with one extra flag:
 ```bash
 xanosdk init my-app --from workspace          # your real workspace (the one your login is scoped to)
 xanosdk init my-app --from ephemeral:my-env   # a named ephemeral environment
-xanosdk init my-app --from local-engine:<name> # a running local engine (`local-engine list`) — no login
+xanosdk init my-app --from local:<name> # a running Xano Engine (`local list`) — no login
 xanosdk init my-app --from ./ws.json          # a bundle already on disk — offline, no login
 ```
 
 `--from` takes any backend in [the CLI's one grammar](cli.md#naming-a-backend) —
-`workspace`, `ephemeral[:<name>]`, `local-engine[:<name>]`, `tenant:<name>`, `release:<name>` —
+`workspace`, `ephemeral[:<name>]`, `local[:<name>]`, `tenant:<name>`, `release:<name>` —
 or a bundle path. Unlike most commands it has no default: a pull names its source.
 
 Everything else about the project is unchanged: `--framework`, the theme flags, `--no-agents-md` and
@@ -32,7 +32,7 @@ that already has its own shell, or to read one.
 ```bash
 xanosdk generate workspace                    # → ./xano
 xanosdk generate release:v1 --out ./backend   # a stored release
-xanosdk generate ephemeral:my-env             # also tenant:<name>, local-engine[:<name>]
+xanosdk generate ephemeral:my-env             # also tenant:<name>, local[:<name>]
 xanosdk generate ./ws.json                    # a bundle on disk — offline, no login
 xanosdk generate workspace --branch staging   # --branch applies to `workspace` only
 ```
@@ -170,7 +170,8 @@ over a `xano/` no decode wrote follows the same rules.
 > ⚠️ **`xano/` is your source once pulled — commit it.** A refresh overwrites the files it
 > decodes, so commit before one (a directory that isn't a previous pull still needs `--force`).
 > It carries schema only — no table rows or stored files.
-> `xanosdk deploy` sends it to a disposable ephemeral environment as a *full replace*;
+> `xanosdk deploy` sends it to the Xano Engine on this machine (`--ephemeral`: a disposable
+> ephemeral environment) as a *full replace*;
 > `xanosdk promote <release>` or `xanosdk deploy --to workspace` merges it into your real
 > workspace. Workspace env vars are declared by name only — their values never enter the tree.
 

package/guides/codes.md

@@ -35,7 +35,7 @@ Printed as `! …` on stderr, and as `{ code, message }` in a `--json` document'
 
 | Code | Meaning |
 |---|---|
-| `agents.refresh-failed` | A managed agent file (AGENTS.md, …) could not be refreshed; the compile itself went on. |
+| `agents.refresh-failed` | A managed block (AGENTS.md, the README's Built-with footer) could not be refreshed; the compile itself went on. |
 | `agents.symlink` | … is a symlink — left it and its target untouched. |
 | `branch.deletion` | … will be permanently deleted and CANNOT be recovered: |
 | `branch.inventory-unknown` | The branch inventory could not be read, so what this wipe destroys is UNKNOWN. |
@@ -97,15 +97,15 @@ Printed as `! …` on stderr, and as `{ code, message }` in a `--json` document'
 | `init.verify-failed` | Verification FAILED — the objects listed above do not re-export as they were pulled. |
 | `init.workflow-exists` | … already exists — moving the new workflow there replaces it. |
 | `landing.record-failed` | The prune landed, but … could not be updated: … |
-| `local-engine.foreign` | Left running, not started by xanosdk: … |
-| `local-engine.import-failed` | The import failed — the engine is still running, so nothing needs restarting: |
-| `local-engine.list-failed` | Could not list running engines, so none are shown: … |
-| `local-engine.not-pinned` | No package.json in …, and it is not a Xano SDK project, so the local engine was not pinned — this deploy runs the latest engine. |
-| `local-engine.pin-unusable` | The project's pinned engine version could not be read and was not used. |
-| `local-engine.runtime-kept` | Kept the unpacked runtime (…): … still running on it. |
-| `local-engine.stale` | … is running …, but the engine cached here is …. |
-| `local-engine.stop-failed` | … was listed as running but did not stop…. |
-| `local-engine.version-invalid` | … This deploy runs the latest local engine and the field is left as written — set it to a version like "v0.1.5", or run `xanosdk local-engine update` to pin… |
+| `local.foreign` | Left running, not started by xanosdk: … |
+| `local.import-failed` | The import failed — the engine is still running, so nothing needs restarting: |
+| `local.list-failed` | Could not list running engines, so none are shown: … |
+| `local.not-pinned` | No package.json in …, and it is not a Xano SDK project, so the Xano Engine was not pinned — this deploy runs the latest engine. |
+| `local.pin-unusable` | The project's pinned engine version could not be read and was not used. |
+| `local.runtime-kept` | Kept the unpacked runtime (…): … still running on it. |
+| `local.stale` | … is running …, but the engine cached here is …. |
+| `local.stop-failed` | … was listed as running but did not stop…. |
+| `local.version-invalid` | … This deploy runs the latest Xano Engine and the field is left as written — set it to a version like "v0.1.5", or run `xanosdk local update` to pin one. |
 | `lock.ceded-canonical` | A lock entry kept its guid but ceded its canonical to a live object; a rename moves the entry so the object keeps its URL. |
 | `lock.created-in-ci` | This lock was created in CI, which means the repository does not have one. |
 | `lock.dropped-entry` | A stale lock entry was dropped because its identity reappeared under a live name (a reverted or identity-keeping rename). |
@@ -142,7 +142,9 @@ Printed as `! …` on stderr, and as `{ code, message }` in a `--json` document'
 | `module.install-failed` | … failed — the module was not added. |
 | `module.kind-unknown` | … does not declare a module kind we recognize, so it is read as an ordinary package. |
 | `module.legacy-peer-deps` | Installed with --legacy-peer-deps: …. |
-| `module.load-failed` | Could not load …/index.ts to update what the module left behind (…). |
+| `module.load-failed` | Could not load …/index.ts to … (…). |
+| `module.peer-mismatch` | The project already declares a peer a toolchain module needs, and the installed version falls outside the module's range; it was left as it is. |
+| `module.peer-not-added` | A peer a toolchain module needs could not be added as a direct dependency; the line names the command that adds it. |
 | `module.peer-unresolved` | … declares a peer range this project does not satisfy; --legacy-peer-deps did not resolve it either. |
 | `module.removed-from-marketplace` | … has been removed from the marketplace. |
 | `module.sdk-skew` | … requires `@xano/sdk` … — the module was not added. |
@@ -224,6 +226,7 @@ Printed as `! …` on stderr, and as `{ code, message }` in a `--json` document'
 | `release.seed-rows-not-decoded` | … carries seed rows for …, and a decoded tree carries no rows — they are not in …/. |
 | `release.transfer-cancelled` | Transfer cancelled — nothing was imported. |
 | `routes.cli-skew` | This CLI is another version than the project's installed SDK, so it left the route table for the installed CLI to render. |
+| `routes.module-failed` | A toolchain module could not generate its section of `routes.gen.ts`; the rest was refreshed and its previous block, if any, was kept. |
 | `routes.not-written` | The route table (`routes.gen.ts`) was not written this run; the line says why and what writes it. |
 | `routes.realtime-unresolved` | …: leaving out … — … — whose canonical URL token resolves nowhere, along with their channels. |
 | `secrets.cleartext-export` | … carries … in cleartext — written owner-only (0600); do not commit it. |
@@ -248,6 +251,7 @@ Printed as `! …` on stderr, and as `{ code, message }` in a `--json` document'
 | `static.teardown-unknown` | Could not read …'s static hosting, so this cannot say whether a frontend serves there — this replace takes down any that does. |
 | `static.unconfirmed-live` | Could not confirm the frontend is live within the wait window — the build uploaded and should come online shortly. |
 | `static.upload-failed` | The static-host upload failed — the backend deploy stands: |
+| `sync.record-failed` | The … succeeded, but its sync baseline could not be recorded in …: … |
 | `tenant.deploy-partial` | The deploy stopped partway: … release "…" declares… — answered as a NOT NULL violation, though the release makes no field required: the value converts to nul… |
 | `tenant.deploy-unconfirmed` | Compare its `deployedAt` and `deployedReleaseId` with what they were before this deploy (deployedAt …, deployedReleaseId …). |
 | `tenant.identities-unchecked` | Whether this release's names and pinned public URL slugs are free on … was not checked — …. |
@@ -309,6 +313,7 @@ Raised while a workspace compiles (`export`, `deploy`, `release`, …). A warnin
 | `field.email-default-invalid` | The `default` at … is …, which is not an email address — every insert or request that leaves the field out is refused "Invalid email format.". |
 | `field.enum-default-not-a-value` | The `default` at … is …, which is not one of the enum's values (…) — a value no request can send back. |
 | `field.input-default-invalid` | The `default` at … is …, which … — every request that leaves the input out is refused. |
+| `field.input-required-default-ignored` | The `default` at …, input "…" is …, but the input is `required: true` — the engine refuses a request that leaves a required input out ("Missing param") befor… |
 | `field.vector-not-nullable` | table "…", column "…" is a vector with `nullable: false` and no default — an empty default becomes NULL only on a nullable column, and `''` is not a vector,… |
 | `function.reserved-input-name` | function "…": the input name `…` is reserved by the engine — a call passes its arguments keyed by input name, and the engine skips a `…` key when it evaluate… |
 | `guard.role-unsatisfiable` | A guard.role on a table passed by name checks a column the table lacks, or a role its enum column cannot hold. |