@xanots/sdk 0.0.9 → 0.0.10

package/llms.txt

@@ -1,4 +1,4 @@
-# xanots v0.0.9
+# xanots v0.0.10
 
 > TypeScript SDK that compiles a typed Xano workspace into the importable packageExport JSON bundle.
 
@@ -50,7 +50,7 @@ installed), so a plain file read resolves them at the version you have.
 - [Column and input types](llms/fields.md): Read when declaring a table column (`f.*`) or a function/query input (`input.*`) — a type's options and accessor methods, and the `s.precondition` error/status contract that rides the same catalog.
 - [Filter catalog](llms/filters.md): Read when piping a value through `fl.*` — the full catalog with each filter's argument types.
 - [Lambda bodies (JavaScript)](llms/lambda.md): Read when writing a JavaScript body, or weighing whether to reach for one at all — `lam.fn`, `fl.lambda`, `fl.reduce`, `s.lambda`. Lambda workers are a bounded shared resource, and each surface binds a different set of identifiers.
-- [Lock file](llms/lock.md): Read when a `xano.lock` exists or should — renaming/pruning/adopting identities, seeding the lock programmatically, or asking which commands write it.
+- [Lock file](llms/lock.md): Read when a `xano.lock` exists or should — renaming/pruning/importing identities, seeding the lock programmatically, or asking which commands write it.
 - [Legacy paradigms and retired statements](llms/legacy.md): Read when the code was PULLED from an existing Xano instance rather than authored here — how a codegen'd tree reads and the three shapes in it that must not be "fixed", plus a `raw({ name: "mvp:…" })` statement, a `realtimeTrigger()`, or any name the catalogs do not list.
 - [Statement catalog](llms/statements-catalog.md): Read for the field signature of a specific statement — every surface, grouped by `s.*` namespace. Look here after the control-flow core in the router does not cover what you need.
 
@@ -115,7 +115,7 @@ which fails with a "must be ES modules" error until you switch it to module.
 
 Set `canonical` on every `apiGroup`. The engine mints the URL token server-side, so
 without one a group's client paths are unresolvable until a lock exists: the bundle
-exports fine and `xanots paths` / `getPath()` then fail on the very queries it just
+exports fine and `xanots routes` / `getPath()` then fail on the very queries it just
 built. An explicit `canonical` resolves them from the source alone.
 
 Build warnings: `export()` prints the shapes that deploy clean and then do the wrong
@@ -134,7 +134,7 @@ api-group/toolset canonical in a lock file written BESIDE THE ENTRY FILE —
 To rename an object: rename in code, export (stderr prints the exact fix-up), run
 `xanots lock rename <kind> <old> <new>`, export again — the original guid is emitted
 under the new name, so the engine renames in place instead of delete+create. Taking
-over an existing workspace: `xanots lock adopt <its-packageExport.json>` first, then
+over an existing workspace: `xanots lock import <its-packageExport.json>` first, then
 export. Pruning, programmatic seeding, and which commands write the lock:
 `llms/lock.md`.
 
@@ -147,19 +147,19 @@ environment and prints its URL.
 AND records — before importing. The blast radius is a disposable environment, not a
 production workspace, but confirm with the user before the first run.
 
-**Two destinations, and the choice changes more than the target.**
+**One destination, and no flag for it.**
 
-- `--dest ephemeral` (DEFAULT) — a NAMED, workspace-scoped, auto-expiring tenant
-  (~1h; `--expires-hours` 1–72 at create time). The active one is tracked in
+- `xanots deploy` writes to a NAMED, workspace-scoped, auto-expiring ephemeral tenant
+  (~1h; `--expires-hours` 1–72 at create time), and to nothing else — an `--env` here
+  is a usage error, not a choice. The active env is tracked in
   `./.xano/ephemeral.json`, so deploying again REFRESHES it and the URL is unchanged;
   if it expired or was swept, a fresh one is created and the new URL is called out.
   `--static` puts the frontend ON THE EPHEMERAL, so backend and frontend share one
   disposable environment.
   ⚠ Only the BACKEND URL survives a refresh: the replace clears static hosting too,
   so `--static` publishes a NEW host every run and the previous URL stops serving.
-- `--dest sandbox` — your single throwaway tenant, no expiry. `--static` puts the
-  frontend on your OWN (parent) workspace instead, because the sandbox tenant does
-  not serve static hosting.
+- `xanots status` names the env this project last deployed to, its URL and its expiry,
+  without your having to remember which one it was.
 - `xanots release` promotes to your INSTANCE workspace and MERGES, not replaces:
   adds/updates what you define, deletes nothing, writes no rows. Destruction is
   opt-in per flag, previewed + confirmed, and can drop a table WITH its rows.
@@ -182,7 +182,7 @@ host falls back to '', and every call 404s off the dev server.
 ⚠ It is INJECTED in bracket form — `window["XANO_HOST"]="…"` — so verifying a deploy
 by grepping `window.XANO_HOST` matches nothing and reads as a failed inject. Grep the
 bare `XANO_HOST` token.
-⚠ `xanots validate` ignores the deploy login and reads `XANO_VALIDATE_INSTANCE` /
+⚠ `xanots preflight` ignores the deploy login and reads `XANO_VALIDATE_INSTANCE` /
 `XANO_VALIDATE_TOKEN` (+ optional `XANO_VALIDATE_WORKSPACE_ID`) from the environment.
 **Displaying a stored file.** A file column comes back as `{ path, name, type, size,
 meta, access, url }`. ⚠ Do NOT use its `url`: on a tenant-scoped environment that field
@@ -332,7 +332,7 @@ Non-obvious authoring rules:
   never removes it. The floor is the RUNTIME, not the def: a second def, or a much richer
   one, adds ~1 kB. So the cost is paid by importing ANY def at all, and reducing what a
   def does will not reduce it.
-  Fix: `xanots paths <entry> --emit xano/routes.gen.ts` (`routes` is an accepted alias) — verbs, paths, and sockets as
+  Fix: `xanots routes <entry> --emit xano/routes.gen.ts` (`paths` is an accepted alias) — verbs, paths, and sockets as
   plain data importing NOTHING, still compile-checked: `routePath("blog/{slug}", { slug })`,
   `channelPath("rooms/{room_id}", { room_id })`, `socketUrl("chat", baseUrl)` (tenant base
   URLs lifted to `wss://h/ws/<tenant>:<canonical>`). A rename is a type error, not a 404.
@@ -419,19 +419,10 @@ Non-obvious authoring rules:
   credential the runner has. As a file that triple is `{ "type": "token",
   "instance_base_url": …, "workspace_id": <n>, "meta_api_token": … }`. The older
   `$XANO_REFRESH_TOKEN` + `$XANO_CLIENT_ID` pair still works but ROTATES: single-use.
-- **Event-driven objects fire on an EPHEMERAL, not in the sandbox.** A `task`
-  (scheduled), an `mcpServer`, and every trigger — `tableTrigger` included — run normally
-  on an ephemeral env, which is `deploy`'s DEFAULT destination. So test an event-driven
-  design (screen-on-insert, cron cleanup, MCP tool call) by deploying it and letting it
-  run.
-  ⚠ Under `--dest sandbox` they import cleanly but their stacks NEVER execute, and there
-  is no way to fire one manually — an insert on a bound table does not run its
-  `tableTrigger`, and the design silently does nothing. Only synchronously-invoked objects
-  (queries, functions, and the agents an endpoint calls with `s.ai.agent.run`) run there.
-  If you must stay on the sandbox, verify the logic out of band: factor the body into a
-  `defineFunction` (or a callable `query`) and invoke it directly — a `tableTrigger` that
-  screens a row on insert should delegate to a function a `query` can also call via
-  `s.function.run`, and you assert against that.
+- **Event-driven objects fire on an EPHEMERAL.** A `task` (scheduled), an `mcpServer`,
+  and every trigger — `tableTrigger` included — run normally on an ephemeral env, which
+  is where `deploy` sends them. So test an event-driven design (screen-on-insert, cron
+  cleanup, MCP tool call) by deploying it and letting it run.
 - **Zero-based numeric keys make `c.obj` a LIST.** `c.obj({ "0": "a" })` evaluates to
   `["a"]`: a numeric key IS an index in the engine's data model, so keys that are exactly
   `0..n-1` come back as a list with HTTP 200 and no error. Write `c.array([...])` when you