@lotics/cli 0.183.0 → 0.184.0

package/AGENTS.md

@@ -5,7 +5,7 @@ conventions are, and where the traps are.
 
 | Read | For |
 |---|---|
-| `lotics --help` | The verb inventory (§ COMMANDS) and global flags. Authoritative; never stale. |
+| `lotics --help` | The verb inventory (§ COMMANDS) and global flags. The verb LIST is generated and never stale; the prose beside each verb is hand-written, so where it disagrees with `docs/cli_reference.md`, the reference wins. |
 | `lotics tools` · `lotics tools <name>` | The agent tool registry and one tool's full JSON Schema. |
 | `lotics docs` · `lotics docs <area>` | Every reference the packages installed beside the project actually ship — `@lotics/app-sdk`, `@lotics/ui` and the document engines each carry their own, and this index only covers THIS package. Discovered by looking, not by a list, so it reports the installed VERSION of each: a doc always describes the code that is really there. |
 | [docs/building_an_app.md](./docs/building_an_app.md) | The SEQUENCE — scaffold, model, types, queries, workflows, screens, ship — and the deploy-free inner loop. The other references describe contracts; this one is the order they go in and why. Read it once before starting an app. |
@@ -29,7 +29,8 @@ Several capabilities exist **only** as commands and appear nowhere in `lotics to
 file and running a bound app agent are the two that most often get mistaken for missing. Concluding
 "the platform can't do X" from the tool list alone is a mistake; check both.
 
-⚠️ **`lotics <subcommand> --help` prints the generic top-level help.** It does not describe the
+⚠️ **`lotics <subcommand> --help` prints the generic top-level help**, except `lotics report --help`
+and a bare `lotics auth` / `xlsx` / `docx`, which print their own. It does not describe the
 subcommand, so an unhelpful response there is *not* evidence the subcommand is absent. To find out
 whether something exists, read `lotics --help` § COMMANDS — the whole section, not a narrow grep.
 
@@ -37,8 +38,9 @@ whether something exists, read `lotics --help` § COMMANDS — the whole section
 
 - **Scope is resolved per invocation.** `LOTICS_ORG` / `LOTICS_WORKSPACE` (or `LOTICS_API_KEY`) scope a
   single call without changing the active org or a directory pin — the safe way to touch one tenant
-  from a shell serving many. Every command echoes its resolved target to **stderr** (`lotics → <org> /
-  <workspace>`); read it back before trusting a write. Resolution precedence is in README § Organizations.
+  from a shell serving many. Every command that resolves a workspace echoes its target to **stderr**
+  (`lotics → <org> / <workspace>`); read it back before trusting a write. `file preview <fil_…>` is
+  the one credentialed command with no echo. Resolution precedence is in README § Organizations.
 - **Large payloads bypass `ARG_MAX`** — `lotics run <tool> @args.json` or piped stdin. A leading `@` is
   unambiguously a file path (JSON args start with `{`).
 - **stdout is the payload, stderr is the narration.** Progress, status lines, and the target echo go to
@@ -48,7 +50,8 @@ whether something exists, read `lotics --help` § COMMANDS — the whole section
   (`run_app_workflow`, `run_app_agent`, `run_app_query`). An `app` command exists only for work no
   tool call can do: scaffold, build, typecheck, serve, or read and push a local file.
 - **Exit codes are assertable, and they report the WORK rather than the call.** `lotics run` exits
-  non-zero when the result's own envelope carries a failed `status` (`error`/`failed`/`cancelled`),
+  non-zero when a `run_app_workflow` or `run_app_agent` result's own envelope carries a failed
+  `status` (`error`/`failed`/`cancelled`) — any other tool's top-level status is data and exits 0 —
   so `lotics run … && next-step` cannot walk past a refused run; `workspace doctor` exits non-zero on
   findings. An unrecognized status exits 0 — the list is an allowlist of failure, so a status added
   later never turns a working script red — and a parked run (`awaiting_input`) is not a failure.
@@ -88,11 +91,11 @@ whether something exists, read `lotics --help` § COMMANDS — the whole section
   | `queries`, `capabilities` | the manifest | `app deploy` — re-synced on every one (an absent `capabilities` block turns them all OFF) |
   | `knowledge` | the manifest | nothing, until the app is published as a starter — it declares which docs ship with it |
   | `workflows` | the workflow row's verified contract | `app workflow set`, which type-checks the BODY against your declaration and refuses a schema the body cannot satisfy |
-  | `agents` | the app row | **nothing.** It is a mirror: `app codegen` re-silvers it from the app, and an agent is changed with `set_app_agent` |
+  | `agents` | `inputs`/`outputs`: the manifest. Everything else: the app row | `app agent set`, and `app deploy`, which pushes a diverged `inputs`/`outputs` before it ships. The rest is a mirror `app codegen` re-silvers, changed with `set_app_agent` |
 
-  `agents` is the one that bites, because editing a mirror still retypes `useAgentRun` — green
-  locally, unchanged in production. `app codegen` reverts such an edit and `app deploy` refuses while
-  the two disagree. An agent's PROSE is not in the manifest at all: it lives in
-  `src/agents/<alias>.md` and is pushed by `app agent set`.
+  `agents` is the one that bites, because the two halves of the same block behave differently:
+  editing `tool_names` or `knowledge_doc_ids` still retypes `useAgentRun` — green locally, unchanged
+  in production, and reverted by the next `app codegen`. An agent's PROSE is not in the manifest at
+  all: it lives in `src/agents/<alias>.md` and is pushed by `app agent set`.
 - **OAuth connections.** Attaching a connected account is web-only; the CLI can list them.
 - **Anything needing a browser.** `app dev` and `file preview` shell out to a local Chrome.

package/README.md

@@ -70,7 +70,7 @@ irm https://lotics.ai/install.ps1 | iex           # Windows PowerShell — no No
 Re-run whichever installer you used; `npm install -g @lotics/cli@latest` updates an npm install.
 The CLI names the right one for the copy you are running when it sees a newer version.
 
-The CLI checks for updates once per day and prompts when a new version is available.
+The CLI checks for updates once per day and prints a note on stderr, naming the right installer, when a new version is available.
 
 ## Authentication
 
@@ -94,7 +94,7 @@ lotics auth api-key                  # interactive prompt
 lotics auth api-key ltk_...          # registers the key's org as a profile (now active)
 ```
 
-Run `lotics auth logout [<name|id>]` to remove a profile (default: the active org), or `lotics auth logout --all` to wipe the store.
+Run `lotics auth logout [<name|id>]` to remove a profile (default: the active org), or `lotics auth logout --all` to wipe the store. Inside a pinned directory the bare form removes the **pin**, not a profile — name the org to remove its credential.
 
 ## Organizations
 
@@ -120,7 +120,7 @@ lotics workspace select wks_...     # records the workspace in the local pin
 
 Each worktree resolves independently; switching the global default in another shell leaves pinned worktrees untouched. `.lotics/` should be gitignored.
 
-Every command names its target before it acts — `lotics → <org> / <workspace>` on **stderr**, so stdout stays clean for piping. When nothing in the directory or environment chose the org and it came from the machine-wide default, the line says so and prints the `--local` command to pin — that default is the one another shell can move between two of your commands. `lotics auth whoami` reports the same resolution on demand, including which source won.
+Every command that resolves a workspace names its target before it acts — `lotics → <org> / <workspace>` on **stderr**, so stdout stays clean for piping. When nothing in the directory or environment chose the org and it came from the machine-wide default, the line says so and prints the `--local` command to pin — that default is the one another shell can move between two of your commands. `lotics auth whoami` reports the same resolution on demand, including which source won.
 
 ### Resolution precedence
 

package/dist/src/cli.js

@@ -44602,6 +44602,19 @@ var LoticsClient = class {
   async listStarterVersions(starter_id) {
     return this.request("GET", `/v1/starters/${encodeURIComponent(starter_id)}/versions`);
   }
+  /**
+   * One version's contract — what a copy of it is supposed to produce. The
+   * history above omits it (heavy per row); this is the read that carries it,
+   * so a check compares a copy against the declaration itself rather than
+   * against a description of it. Admin-only; cross-tenant by id like
+   * `getStarter`.
+   */
+  async getStarterVersion(starter_id, version2) {
+    return this.request(
+      "GET",
+      `/v1/starters/${encodeURIComponent(starter_id)}/versions/${encodeURIComponent(String(version2))}`
+    );
+  }
   /**
    * Workspace-wide dangling-reference sweep — active app/workflow artifacts
    * whose prefixed schema ids no longer resolve. Backs
@@ -44669,13 +44682,13 @@ var LoticsClient = class {
         const fields = table.fields.flatMap((field) => {
           if (field === null || typeof field !== "object") return [];
           const f = field;
-          if (typeof f.key !== "string" || typeof f.name !== "string") return [];
+          if (typeof f.key !== "string" || typeof f.name !== "string" || typeof f.type !== "string") return [];
           const options = Array.isArray(f.options) ? f.options.flatMap((opt) => {
             if (opt === null || typeof opt !== "object") return [];
             const o = opt;
             return typeof o.key === "string" && typeof o.name === "string" ? [{ id: o.key, label: o.name }] : [];
           }) : void 0;
-          return [{ id: f.key, name: f.name, ...options && options.length > 0 ? { options } : {} }];
+          return [{ id: f.key, name: f.name, type: f.type, ...options && options.length > 0 ? { options } : {} }];
         });
         return { id: table.id, name: table.name, fields };
       })
@@ -45429,6 +45442,25 @@ function resolveContext(flags, appWorkspaceId) {
   const envOrg = process.env.LOTICS_ORG;
   const envWorkspace = process.env.LOTICS_WORKSPACE;
   const wsOverride = flags.workspace ?? envWorkspace;
+  if (flags.org) {
+    if (flags.apiKey) {
+      throw new Error("Pass --org or --api-key, not both \u2014 they name two different credentials.");
+    }
+    const resolved = resolveProfileByNameOrId(loadGlobalConfig()?.profiles ?? {}, flags.org);
+    if (!resolved) {
+      throw new Error(
+        `--org "${flags.org}" matches no saved credential. Run "lotics org" to list, or "lotics auth api-key <key>" to add one.`
+      );
+    }
+    const [orgId, profile] = resolved;
+    return {
+      apiKey: profile.api_key,
+      orgId,
+      orgName: profile.org_name,
+      workspaceId: wsOverride ?? profile.workspace_id,
+      source: "flag_org"
+    };
+  }
   if (flags.apiKey) {
     return { apiKey: flags.apiKey, workspaceId: wsOverride, source: "flag" };
   }
@@ -45679,7 +45711,7 @@ function resultSideEffects(result) {
 }
 
 // src/version.ts
-var VERSION = "0.183.0";
+var VERSION = "0.184.0";
 
 // src/timezone.ts
 function machineTimezone() {
@@ -45966,8 +45998,10 @@ var COMMANDS = [
       "                                       shipping: agent schemas vs the live app, workflow",
       "                                       declarations and BODIES vs what is live, aliases",
       "                                       the code calls but nothing bound, undeclared",
-      "                                       capabilities, query drift. Exits 1 on what a",
-      "                                       deploy would refuse, so CI can gate on it",
+      "                                       capabilities, query drift. Plus the one rule no",
+      "                                       deploy runs: a concrete id or an id-shaped",
+      "                                       placeholder in source a starter would ship.",
+      "                                       Exits 1 on any of it, so CI can gate on it",
       "  lotics app workflow set <alias>      Push the edited src/workflows/<alias>.ts body",
       "                                       through set_app_workflow (server verifies)",
       "  lotics app workflow pull             Rewrite src/workflows/*.ts from the server",
@@ -71253,6 +71287,203 @@ function checkWorkflowBodies(tsApi, aliases) {
   }));
 }
 
+// ../../node_modules/nanoid/index.js
+import { webcrypto as crypto3 } from "node:crypto";
+var POOL_SIZE_MULTIPLIER = 128;
+var pool;
+var poolOffset;
+function fillPool(bytes) {
+  if (bytes < 0) throw new RangeError("Wrong ID size");
+  try {
+    if (!pool || pool.length < bytes) {
+      pool = Buffer.allocUnsafe(bytes * POOL_SIZE_MULTIPLIER);
+      crypto3.getRandomValues(pool);
+      poolOffset = 0;
+    } else if (poolOffset + bytes > pool.length) {
+      crypto3.getRandomValues(pool);
+      poolOffset = 0;
+    }
+  } catch (e) {
+    pool = void 0;
+    throw e;
+  }
+  poolOffset += bytes;
+}
+function random(bytes) {
+  fillPool(bytes |= 0);
+  return pool.subarray(poolOffset - bytes, poolOffset);
+}
+function customRandom(alphabet, defaultSize, getRandom) {
+  let safeByteCutoff = 256 - 256 % alphabet.length;
+  if (safeByteCutoff === 256) {
+    let mask = alphabet.length - 1;
+    return (size2 = defaultSize) => {
+      if (!size2) return "";
+      let id = "";
+      while (true) {
+        let bytes = getRandom(size2);
+        let i2 = size2;
+        while (i2--) {
+          id += alphabet[bytes[i2] & mask];
+          if (id.length >= size2) return id;
+        }
+      }
+    };
+  }
+  let step = Math.ceil(1.6 * 256 * defaultSize / safeByteCutoff);
+  return (size2 = defaultSize) => {
+    if (!size2) return "";
+    let id = "";
+    while (true) {
+      let bytes = getRandom(step);
+      let i2 = step;
+      while (i2--) {
+        if (bytes[i2] < safeByteCutoff) {
+          id += alphabet[bytes[i2] % alphabet.length];
+          if (id.length >= size2) return id;
+        }
+      }
+    }
+  };
+}
+function customAlphabet(alphabet, size2 = 21) {
+  return customRandom(alphabet, size2, random);
+}
+
+// ../shared/src/id.ts
+var ID_ALPHABET = "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz";
+var ID_LENGTH = 12;
+var nanoid3 = customAlphabet(ID_ALPHABET, ID_LENGTH);
+function generatePrefixedId(prefix) {
+  return `${prefix}_${nanoid3()}`;
+}
+var RECORD_ID_PATTERN = new RegExp(`^rec_[${ID_ALPHABET}]{${ID_LENGTH}}$`);
+function generateWorkspaceId() {
+  return generatePrefixedId("wsp");
+}
+function generateTableId() {
+  return generatePrefixedId("tbl");
+}
+function generateGroupId() {
+  return generatePrefixedId("grp");
+}
+function generateAppId() {
+  return generatePrefixedId("app");
+}
+function generateDocumentTemplateId() {
+  return generatePrefixedId("dtl");
+}
+
+// ../shared/src/table_field_keys.ts
+var nanoid4 = customAlphabet(ID_ALPHABET, 6);
+function generateFieldKey() {
+  return `fld_${nanoid4()}`;
+}
+function generateOptionKey() {
+  return `opt_${nanoid4()}`;
+}
+
+// ../shared/src/concrete_ids.ts
+function bodyWidth(id) {
+  return id.length - id.indexOf("_") - 1;
+}
+var GENERATED_BODY_WIDTH = /* @__PURE__ */ new Map([
+  ["tbl", bodyWidth(generateTableId())],
+  ["fld", bodyWidth(generateFieldKey())],
+  ["opt", bodyWidth(generateOptionKey())],
+  ["dtl", bodyWidth(generateDocumentTemplateId())],
+  ["grp", bodyWidth(generateGroupId())],
+  ["wsp", bodyWidth(generateWorkspaceId())],
+  ["app", bodyWidth(generateAppId())]
+]);
+function widthOf(prefix) {
+  const width = GENERATED_BODY_WIDTH.get(prefix);
+  if (width === void 0) throw new Error(`concrete_ids: no generator registered for ${prefix}_`);
+  return width;
+}
+var SCHEMA_PREFIXES = ["tbl", "fld", "opt", "dtl", "grp"];
+var SHORTEST_SCHEMA_BODY = Math.min(...SCHEMA_PREFIXES.map(widthOf));
+var CONCRETE_ID_SCAN = new RegExp(
+  `(?<![0-9A-Za-z])(?:${SCHEMA_PREFIXES.join("|")})_[0-9A-Za-z]{${SHORTEST_SCHEMA_BODY},}`,
+  "g"
+);
+var WORKSPACE_ID_SCAN = new RegExp(
+  `(?<![0-9A-Za-z])(?:organization-(?:[0-9a-z]+-)?[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|wsp_[0-9A-Za-z]{${widthOf("wsp")}}(?![0-9A-Za-z])|app_[0-9A-Za-z]{${widthOf("app")}}(?![0-9A-Za-z])|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})`,
+  "g"
+);
+var ID_PLACEHOLDER_SCAN = new RegExp(
+  `(["'\`])((?:${SCHEMA_PREFIXES.join("|")})_[0-9A-Za-z]+)\\1`,
+  "g"
+);
+function isGeneratedIdBody(id) {
+  const underscore = id.indexOf("_");
+  if (underscore === -1) return true;
+  return /[0-9A-Z]/.test(id.slice(underscore + 1));
+}
+function isBelowGeneratedWidth(token) {
+  const underscore = token.indexOf("_");
+  const width = GENERATED_BODY_WIDTH.get(token.slice(0, underscore));
+  if (width === void 0) return false;
+  return token.length - underscore - 1 < width;
+}
+var SCAN_EXTENSIONS = [".ts", ".tsx", ".js", ".jsx", ".mjs", ".cjs", ".html", ".css", ".json"];
+var SCAN_FILE_MAX_BYTES = 1024 * 1024;
+function normalizeScanPath(path13) {
+  return path13.replace(/\\/g, "/").replace(/^\.\//, "").replace(/^\/+/, "");
+}
+function hasScannableExtension(path13) {
+  return SCAN_EXTENSIONS.some((ext) => path13.endsWith(ext));
+}
+function isConcreteIdScanPath(path13) {
+  const name2 = normalizeScanPath(path13);
+  if (name2.endsWith(".md")) return true;
+  if (!name2.startsWith("src/")) return false;
+  if (name2.startsWith("src/workflows/")) return false;
+  return hasScannableExtension(name2);
+}
+function isTestFile(path13) {
+  return /\.(?:test|spec)\.[cm]?[jt]sx?$/.test(path13);
+}
+function isIdPlaceholderScanPath(path13) {
+  const name2 = normalizeScanPath(path13);
+  if (isTestFile(name2)) return false;
+  if (name2.endsWith(".md")) return true;
+  if (name2 === "package.json") return true;
+  if (!name2.startsWith("src/")) return false;
+  return hasScannableExtension(name2);
+}
+function firstLines(text, pattern, keep, into) {
+  text.split("\n").forEach((line, index) => {
+    for (const match2 of line.matchAll(pattern)) {
+      const id = match2[2] ?? match2[0];
+      if (!keep(id) || into.has(id)) continue;
+      into.set(id, index + 1);
+    }
+  });
+  return into;
+}
+function toFindings(path13, rule, lines) {
+  return [...lines].map(([id, line]) => ({ path: path13, line, id, rule }));
+}
+function scanFileForConcreteIds(path13, text) {
+  if (!isConcreteIdScanPath(path13)) return [];
+  const lines = firstLines(text, CONCRETE_ID_SCAN, () => true, /* @__PURE__ */ new Map());
+  firstLines(text, WORKSPACE_ID_SCAN, isGeneratedIdBody, lines);
+  return toFindings(path13, "concrete", lines);
+}
+function scanFileForIdPlaceholders(path13, text) {
+  if (!isIdPlaceholderScanPath(path13)) return [];
+  const lines = firstLines(text, ID_PLACEHOLDER_SCAN, isBelowGeneratedWidth, /* @__PURE__ */ new Map());
+  return toFindings(path13, "placeholder", lines);
+}
+function scanFileForIds(path13, text) {
+  const concrete = scanFileForConcreteIds(path13, text);
+  const seen = new Set(concrete.map((finding) => finding.id));
+  return [...concrete, ...scanFileForIdPlaceholders(path13, text).filter((f) => !seen.has(f.id))].sort(
+    (a, b) => a.line - b.line || (a.id < b.id ? -1 : 1)
+  );
+}
+
 // ../shared/src/agent_instructions.ts
 function agentFilePath(alias) {
   return `src/agents/${alias}.md`;
@@ -72585,6 +72816,44 @@ function readAppSourceText(projectDir) {
   walk2(srcDir);
   return parts.join("\n");
 }
+var ARCHIVE_EXCLUDES = ["node_modules", "dist", ".lotics", "*.tsbuildinfo", ".git"];
+function isArchiveExcluded(name2) {
+  return ARCHIVE_EXCLUDES.some(
+    (pattern) => pattern.startsWith("*") ? name2.endsWith(pattern.slice(1)) : name2 === pattern
+  );
+}
+function scanProjectForIds(projectDir) {
+  const findings = [];
+  const walk2 = (dir) => {
+    for (const entry of fs8.readdirSync(dir, { withFileTypes: true })) {
+      if (isArchiveExcluded(entry.name)) continue;
+      const full = path9.join(dir, entry.name);
+      if (entry.isDirectory()) {
+        walk2(full);
+        continue;
+      }
+      if (!entry.isFile()) continue;
+      const rel = path9.relative(projectDir, full).split(path9.sep).join("/");
+      if (!isConcreteIdScanPath(rel) && !isIdPlaceholderScanPath(rel)) continue;
+      if (fs8.statSync(full).size > SCAN_FILE_MAX_BYTES) continue;
+      findings.push(...scanFileForIds(rel, fs8.readFileSync(full, "utf8")));
+    }
+  };
+  walk2(projectDir);
+  return findings.sort((a, b) => a.path < b.path ? -1 : a.path > b.path ? 1 : a.line - b.line);
+}
+function reportPortabilityIds(findings) {
+  if (findings.length === 0) return;
+  console.error(
+    `
+\u2717 ${findings.length} id${findings.length === 1 ? "" : "s"} here cannot survive a copy into another workspace:`
+  );
+  for (const finding of findings) {
+    console.error(
+      finding.rule === "concrete" ? `  ${finding.path}:${finding.line} \u2014 ${finding.id} is this workspace's own id; address it through the generated .lotics/app_fields aliases (F/OPT), or in prose name the thing by alias.` : `  ${finding.path}:${finding.line} \u2014 ${finding.id} is id-shaped but no generator could have minted it; publish resolves every id against the app's footprint and refuses this one, so write a stand-in that is not id-shaped.`
+    );
+  }
+}
 async function appDeploy(client, args) {
   const projectDir = path9.resolve(args.projectDir ?? process.cwd());
   const meta3 = readAppMeta(projectDir);
@@ -72633,16 +72902,7 @@ async function appDeploy(client, args) {
   try {
     note("Packaging source...");
     await runTar(
-      [
-        "-czf",
-        tmpSource,
-        "--exclude=node_modules",
-        "--exclude=dist",
-        "--exclude=.lotics",
-        "--exclude=*.tsbuildinfo",
-        "--exclude=.git",
-        "."
-      ],
+      ["-czf", tmpSource, ...ARCHIVE_EXCLUDES.map((pattern) => `--exclude=${pattern}`), "."],
       projectDir
     );
     note("Packaging dist...");
@@ -72817,10 +73077,14 @@ async function appCheck(client, args = {}) {
   warnIfProjectFootguns(projectDir, sourceText);
   warnIfUnbranded(app);
   warnIfUndescribed(app);
-  if (!nothingPending(pending)) {
+  const unportable = scanProjectForIds(projectDir);
+  reportPortabilityIds(unportable);
+  if (!nothingPending(pending) || unportable.length > 0) {
     process.exit(1);
   }
-  console.error("Checked the app's bindings, capabilities and agent schemas \u2014 nothing blocking.");
+  console.error(
+    "Checked the app's bindings, capabilities, agent schemas and id portability \u2014 nothing blocking."
+  );
 }
 async function pushPendingBindings(client, projectDir, pending) {
   const plan = [
@@ -103441,6 +103705,7 @@ function requireClient(flags, appWorkspaceId) {
   };
 }
 var SOURCE_LABELS = {
+  flag_org: "--org flag",
   flag: "--api-key flag",
   env_key: "LOTICS_API_KEY env",
   env_org: "LOTICS_ORG env",

package/dist/src/client.d.ts

@@ -182,6 +182,54 @@ export interface StarterPublish {
     started_at: string | null;
     finished_at: string | null;
 }
+/**
+ * A published version's contract — the artifact set a copy of it creates.
+ *
+ * Narrowed to what a caller CHECKING a copy reads back. The authoritative shape
+ * is `packageContractSchema`, which lives in `@lotics/shared` — a specifier a
+ * published `.d.ts` cannot resolve, so it is declared here rather than imported,
+ * the same trade the publish shapes above make.
+ */
+export interface StarterVersionContract {
+    /**
+     * One table per entity, scaffolded under `label`, with the columns it
+     * declares — a copy whose table landed with the right NAME and the wrong
+     * columns is the failure a table-name check cannot see.
+     */
+    entities: Array<{
+        alias: string;
+        label: string;
+        fields: Array<{
+            alias: string;
+            label: string;
+            type: string;
+        }>;
+    }>;
+    templates: Array<{
+        alias: string;
+        label: string;
+    }>;
+    apps: Array<{
+        alias: string;
+        name: string;
+        /** The named queries the app's shipped source invokes. */
+        queries: Array<{
+            alias: string;
+            /** Param name → declaration. `required` defaults to TRUE when absent. */
+            params?: Record<string, {
+                required?: boolean;
+            }>;
+        }>;
+    }>;
+    /** The knowledge docs the starter ships, keyed by alias. */
+    knowledge: Record<string, {
+        name: string;
+    }>;
+    /** Sample rows per entity alias — `row_count` is the contract's own count of them. */
+    fixtures: Record<string, {
+        row_count: number;
+    }>;
+}
 /** Advisory knowledge warnings surfaced by a copy (never block). */
 export interface KnowledgeWarnings {
     /** `knowledge_expects` doc names with no matching workspace doc. */
@@ -547,6 +595,17 @@ export declare class LoticsClient {
             created_at: string;
         }>;
     }>;
+    /**
+     * One version's contract — what a copy of it is supposed to produce. The
+     * history above omits it (heavy per row); this is the read that carries it,
+     * so a check compares a copy against the declaration itself rather than
+     * against a description of it. Admin-only; cross-tenant by id like
+     * `getStarter`.
+     */
+    getStarterVersion(starter_id: string, version: number): Promise<{
+        version: number;
+        contract: StarterVersionContract;
+    }>;
     /**
      * Workspace-wide dangling-reference sweep — active app/workflow artifacts
      * whose prefixed schema ids no longer resolve. Backs
@@ -597,6 +656,7 @@ export declare class LoticsClient {
         fields: Array<{
             id: string;
             name: string;
+            type: string;
             options?: Array<{
                 id: string;
                 label: string;

package/dist/src/client.js

@@ -404,6 +404,16 @@ export class LoticsClient {
     async listStarterVersions(starter_id) {
         return this.request("GET", `/v1/starters/${encodeURIComponent(starter_id)}/versions`);
     }
+    /**
+     * One version's contract — what a copy of it is supposed to produce. The
+     * history above omits it (heavy per row); this is the read that carries it,
+     * so a check compares a copy against the declaration itself rather than
+     * against a description of it. Admin-only; cross-tenant by id like
+     * `getStarter`.
+     */
+    async getStarterVersion(starter_id, version) {
+        return this.request("GET", `/v1/starters/${encodeURIComponent(starter_id)}/versions/${encodeURIComponent(String(version))}`);
+    }
     /**
      * Workspace-wide dangling-reference sweep — active app/workflow artifacts
      * whose prefixed schema ids no longer resolve. Backs
@@ -482,7 +492,7 @@ export class LoticsClient {
                 if (field === null || typeof field !== "object")
                     return [];
                 const f = field;
-                if (typeof f.key !== "string" || typeof f.name !== "string")
+                if (typeof f.key !== "string" || typeof f.name !== "string" || typeof f.type !== "string")
                     return [];
                 const options = Array.isArray(f.options)
                     ? f.options.flatMap((opt) => {
@@ -494,7 +504,7 @@ export class LoticsClient {
                             : [];
                     })
                     : undefined;
-                return [{ id: f.key, name: f.name, ...(options && options.length > 0 ? { options } : {}) }];
+                return [{ id: f.key, name: f.name, type: f.type, ...(options && options.length > 0 ? { options } : {}) }];
             });
             return { id: table.id, name: table.name, fields };
         }));

package/docs/building_an_app.md

@@ -236,7 +236,8 @@ actually carries, not what the source says it should.
 
 ```
 npm run typecheck && npm run lint && npm test
-lotics app check                     # every pre-flight a deploy runs, without building or shipping
+lotics app check                     # every pre-flight a deploy runs, without building or shipping,
+                                     # plus the portability gate a starter publish applies
 lotics app deploy -m "<what changed + why>"
 ```
 

package/docs/cli_reference.md

@@ -24,7 +24,7 @@ Per-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. S
 | `lotics run <tool> --json '<json>'` | Execute a tool (full JSON output) |
 | `lotics run <tool>` — **file cells** | A file in a tool's result carries its `fil_…` id and metadata and **no `url`**, on every tool and in both output modes. That is not a broken file — this surface resolves no URL for a cell. Reach the bytes with `lotics file download <file_id>`, which takes the id straight from the cell; the text output says so whenever a result carries one. |
 | — | **Every tool is invoked here, including the ones that RUN something** (`run_app_workflow`, `run_app_agent`, `run_app_query`). What stays an `app` command is work no tool call can do — scaffold, build, typecheck, serve, or read and push a local file. |
-| — | **The exit code reports the WORK, not just the call.** A result whose envelope carries a failed `status` (`error`/`failed`/`cancelled`) exits non-zero and prints `<tool> → <status>: <message>` to stderr, so `lotics run … && next-step` cannot walk past a refused run. The rule is an allowlist of FAILURE — an unrecognized status exits 0, so a status added later never turns a working script red. A parked run (`awaiting_input`) is not a failure: it is waiting for an answer and the work is still live. Only a TOP-LEVEL `status` counts; one inside the data belongs to the data. |
+| — | **The exit code reports the WORK, not just the call — for the two tools that RUN one.** `run_app_workflow` and `run_app_agent` whose envelope carries a failed `status` (`error`/`failed`/`cancelled`) exit non-zero and print `<tool> → <status>: <message>` to stderr, so `lotics run … && next-step` cannot walk past a refused run. The rule is an allowlist of FAILURE — an unrecognized status exits 0, so a status added later never turns a working script red. A parked run (`awaiting_input`) is not a failure: it is waiting for an answer and the work is still live. Only a TOP-LEVEL `status` counts; one inside the data belongs to the data. Any OTHER tool's `status` — `press_button`'s included — is data, and exits 0. |
 | `lotics run <tool> --print-created` | Report the records the call created, grouped by table, with a paste-ready `delete_records` per table and the mandatory caveat naming what cannot be auto-undone (external integrations, notifications, possible sub-workflows). Works for any tool that returns a `side_effects` block, not workflows alone. |
 | `lotics run <tool> --cleanup` | Implies `--print-created`, then runs those deletes — harvested records **only**, never files / external calls / notifications. **Not a rollback**; a rollback is structurally impossible here. A partial cleanup exits non-zero so a script cannot read it as success. |
 | `lotics upload <file\|dir...>` · `--stdin` · `--base64` · `--url <url>` | Upload files/directories via multipart POST to /v1/files. A directory expands to its immediate files; `--as <name>` renames a single upload. **Three alternative byte sources, for a caller that never had the bytes on disk** — an attachment decoded in memory, a generated document, a signed download link — each mutually exclusive with the others and with a path argument: `--stdin` takes raw bytes on stdin, `--base64` takes base64 on stdin (the shape attachments arrive in), `--url <url>` fetches the URL first. `--stdin`/`--base64` REQUIRE `--as`, because stdin carries no filename and the mime type is derived from it; `--url` falls back to `Content-Disposition` then the URL's last path segment. `--base64` decodes STRICTLY — `Buffer.from(s, "base64")` silently skips invalid characters and truncates on bad padding, so a corrupted pipe would otherwise store a short file that only fails when a human opens it. The `--url` fetch happens in the CLI, not the server: the URL comes from the operator running the command, so routing it through the backend would add an SSRF surface to buy what `curl` already does. |
@@ -45,11 +45,11 @@ Per-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. S
 | `lotics starter list` | **Works with no account**, and that is the point: whether to copy a starter or build from scratch is decided before one exists, so requiring a key would mean signing up to learn the answer was no. Unauthenticated it lists what Lotics publishes (`GET /v1/starters/official`, public). Authenticated it is the org shelf — The starters this organization can copy — Lotics-reviewed ones plus its own, each with at least one released version. Deliberately NOT a catalogue of everything published: the server returns exactly what a copy would be allowed to take, so the list can never offer something that then refuses. Admin-only. |
 | `lotics starter show <starter_id>` | One starter's name, description, current version, shelf tile and trust standing (`official` — reviewed by Lotics; `your organization's own`; otherwise `not copyable from this organization`), plus the date it was unpublished once it has been. Read it before copying a starter you did not publish. Admin-only, and readable by id from any org — but an unpublished starter 404s for every org except the one that published it. |
 | `lotics starter init <starter_id>` | **Copy a starter into this workspace.** Server-side it scaffolds the tables and fields, creates the document templates and knowledge docs, inserts the sample records, creates every app the starter carries and materializes each one's queries, workflows and agents onto it — then deploys each app from the dist the starter was published with, rewriting the publisher's sentinel field keys to this workspace's. No build runs anywhere, nothing is written to this machine, and nothing here needs node: the apps are live when the command returns. **What you get is yours outright**: ordinary apps plus ordinary tables, with no link back to the starter, nothing pinned, and nothing to upgrade. Edit any of it — `lotics app pull <app_id>` is how an app's code is edited afterwards. **The publisher's code runs in your workspace as you** — its apps, workflows and agents — which is why provenance is the gate: **copyable only if the starter is Lotics-reviewed or your own organization published it**, enforced server-side; the disclosure is printed (and carried in `--json`'s `warnings`) whenever the starter is not your own. **Refuses a workspace that already has tables** unless `--adopt`: scaffold matches an entity by DISPLAY NAME, so a starter declaring `Contacts` would bind to yours. An app whose deploy failed is reported by name with its reason and the exit is non-zero, but the copy is complete around it — the tables, the records and the app row exist — so it must not be run again; the publisher fixes the starter and it is copied into a fresh workspace. The sign-in link lands on the app when there is one, else on the workspace's app list. `--json` prints one object on stdout instead of progress (the shape is under `lotics setup`). `--no-sample-data` skips the sample records, and a copy that ADOPTS an existing table writes none either — that table already holds real rows, and the fixture set links to itself, so it is all-or-nothing; with them, how many landed is reported. They are ordinary records, delete them whenever. Resolves and ANNOUNCES its workspace first (`lotics → <org> / <workspace>` on stderr). Admin-only. Authoring the registry (`opctl starter publish/unpublish`) stays operator-only. |
-| `lotics starter fixtures capture [--entity <alias> ...] [--limit <n>]` | **(authoring)** Write this app's live records into the project as `fixtures/<entity-alias>.json` — the sample data a starter carries, so a copy lands with something in it. Run from an app project; the app id comes from its manifest. The alias-keyed shape is produced server-side, because the aliases are minted when the starter is extracted and exist nowhere a project can read them. `--entity` is repeatable and comma-separated; omitted, every table the app declares is captured. **Capture a linked set in ONE call** — a link between two rows only resolves within a single capture, so taking companies and contacts separately drops the edge between them (it says so when it happens). `--limit` bounds rows per table (default 10, max 200). **READ WHAT IT WROTE before committing**: these rows are created verbatim in every workspace that copies the starter, so a real customer name, price or address captured here is published. Files, formulas, rollups, lookups and autonumbers are never captured — the platform writes those. Admin-only; writes nothing to the workspace. |
+| `lotics starter fixtures capture [--entity <alias> ...] [--limit <n>]` | **(authoring)** Write this app's live records into the project as `fixtures/<entity-alias>.json` — the sample data a starter carries, so a copy lands with something in it. Run from an app project; the app id comes from its manifest. The alias-keyed shape is produced server-side, because the aliases are minted when the starter is extracted and exist nowhere a project can read them. `--entity` is repeatable and comma-separated; omitted, every table the app declares is captured. **Capture a linked set in ONE call** — a link between two rows only resolves within a single capture, so taking companies and contacts separately drops the edge between them (it says so when it happens). `--limit` bounds rows per table (default 10, max 200 — a higher one is clamped, not refused). **A captured row is written into a copy exactly as it reads here**: a cell the origin left empty stays empty, because the copy's inserts do not apply field defaults. **READ WHAT IT WROTE before committing**: these rows are created verbatim in every workspace that copies the starter, so a real customer name, price or address captured here is published. Files, formulas, rollups, lookups and autonumbers are never captured — the platform writes those. Admin-only; writes nothing to the workspace. |
 | `lotics upgrade` | Update this CLI in place. Runs the same installer a person would, chosen by how THIS copy arrived: an npm install upgrades through npm, a script install re-runs the script — the runtime knows which (the executable is compiled, the npm bin runs under node), so nobody has to. It downloads nothing itself; resolving a version, verifying the checksum and replacing a running executable already exist in the installers, and a second copy of that inside the binary would be a second thing to get right. Replacing the binary while it runs is safe — a rename leaves the running image mapped on unix, and on Windows the installer moves the old aside precisely because the file is in use. Already current is a no-op that says so. Needs no auth. |
 | `lotics docs` \| `lotics docs <area>` | The index of the reference docs, **resolved out of the packages installed beside this project** — never carried by this CLI. **Both levels are discovered by looking**: every `@lotics/*` package carrying an `AGENTS.md` or a `docs/` in any `node_modules/@lotics` from the current directory UPWARD (nearest wins, so a hoisted root copy never shadows the one a project's own imports resolve to), and within each, every area it actually ships. Titles come from each file's own `# heading` and the version from the installed `package.json`, so a doc OR a whole package added upstream appears with no change to this CLI, and a skewed install is visible rather than reassuring. A package's index is named after the package (`lotics docs ui`), never `index`. `@lotics/app-sdk`, `@lotics/ui` and `@lotics/cli` sort first as a reading ORDER, not a filter. Both the index and `<area>` print to **stdout** — the index is the payload of a bare `lotics docs`, so `lotics docs | grep -i excel` works — with only the provenance line on stderr, so `lotics docs ai > ai.md` is the doc alone; a name two packages share is refused with both qualified forms (`lotics docs ui/templates`) rather than resolved silently. Needs no auth. Outside a project only `@lotics/cli`'s own resolve, and it says so. |
 | `lotics report '<json>'` \| `lotics report @report.json` | File a report with the Lotics team about what got in your way. **Covers the classes telemetry structurally cannot see**: a capability that does not exist (no command ran, so nothing was recorded), a command that exited 0 having done the wrong thing, an error whose message did not name the remedy, and anything that made authoring slower than it should be. **A frame, not a paragraph** — `{goal, actual, expected?, tried?, wanted?}`, `goal` and `actual` required, unknown keys dropped rather than refused. **No severity or category.** Ingest is inline JSON, `@file`, or `-` for stdin. A bare sentence is refused with the frame printed beside it, so the fix is one step; a bare invocation prints the frame BEFORE asking for a credential, since someone whose key will not resolve is exactly who has something to report. **Not spooled**: unlike telemetry it posts inline, prints whether it landed, and exits non-zero if it did not, echoing the report back so a failed send never loses it. Runs regardless of `LOTICS_TELEMETRY` — invoking it IS the consent that passive collection needs an opt-in for — but with telemetry off there are no recorded commands to attach, and it says so rather than implying context it does not have. Requires auth. Never paste records, file contents, or credentials. |
-| `lotics app check` | Every pre-flight `deploy` runs, WITHOUT building or shipping. **First, whether this project is even based on the served version** — the one thing a deploy REFUSES outright rather than pushing (the server 409s a stale `prev_version_id`), and the one finding that invalidates every other: a stale tree and the live app are two different apps, so comparing them reports nothing trustworthy. Stale exits 1 naming both versions and stops before the rest; a project with no stamp at all — or an app with no version yet — is a first deploy, not a conflict. `deploy` runs the SAME assertion off the app row it already fetched, so a stale tree fails before it pushes a binding or builds, instead of after the upload arrives and the server 409s. Then: the manifest's agent schemas against the live app row, every binding a deploy would push, aliases the source calls that nothing bound (queries, workflows AND agents), bindings this bundle stopped calling (the same transition — and the same baseline — `deploy` reports, so the two cannot disagree), capability-gated SDK calls the manifest doesn't declare, a missing icon/theme, a missing app `description` (it heads the capability catalog the chat agent reads every turn, and its absence has no other symptom), a `vite.config.ts` that never defines `global`/`__DEV__`, a `window.open` in the app's own source, and an INSTALLED `@lotics/app-sdk` below the version that understands the host's realtime push — read from `node_modules`, not the dependency range, because a caret is minor-locked below 1.0 so `^0.79.x` can never resolve `0.80` and `npm update` does nothing (all three fail ONLY in the deployed app — dev bundles with esbuild and production with rollup, so typecheck, lint, build and `app dev` are all green while react-native-web reads `global.cancelAnimationFrame` as a free variable and the sandboxed iframe drops a popup silently), an agent holding `run_app_query`/`run_app_workflow` with an EMPTY `query_aliases`/`workflow_aliases` (the tool is the capability, the alias list is the reach — empty means every call it makes is refused while the run still COMPLETES, so it surfaces as a model ignoring its prompt; read off the live row, never the manifest, which mirrors those fields but is pushed by no verb), and a notice for any alias the source computes at runtime (invisible to every check here and to `--prune`'s unbind guard). **And whether the kit this app builds against has fallen behind what is published** — `@lotics/ui` and `@lotics/app-sdk`, read from `node_modules` for the same reason as the floor check above: a range keeps accepting, so an app pinned `^44.x` reads healthy for a year, and even an in-range one sits on the lockfile's older patch until `npm update` (never `npm install`, which honours the lock). A MAJOR behind is loud and names the packages actually behind — plus `@lotics/ui`'s `MIGRATION.md`, when ui is one of them, since it is the only half that keeps one; anything smaller is one quiet line, because a warning that fires on every deploy is one the reader stops seeing. The registry lookup is bounded and every failure — offline, slow, private — is silence: a version check must never become a new way for a deploy to fail. Adds no rule of its own — each finding is the same helper `deploy` calls, so a green check means a deploy will not complain. **Exits 1 on what a `deploy` would REFUSE or PUSH** — an agent schema that disagrees with the live app, and any binding the project has ahead of the app (an edited workflow body or declaration, edited agent prose, a changed query). Both are things a deploy would act on, so CI gating on a green check means a deploy has nothing left to do; genuine advisories (capabilities, branding, a runtime-computed alias, orphaned bindings) stay advisory and never fail it. |
+| `lotics app check` | Every pre-flight `deploy` runs, WITHOUT building or shipping. **First, whether this project is even based on the served version** — the one thing a deploy REFUSES outright rather than pushing (the server 409s a stale `prev_version_id`), and the one finding that invalidates every other: a stale tree and the live app are two different apps, so comparing them reports nothing trustworthy. Stale exits 1 naming both versions and stops before the rest; a project with no stamp at all — or an app with no version yet — is a first deploy, not a conflict. `deploy` runs the SAME assertion off the app row it already fetched, so a stale tree fails before it pushes a binding or builds, instead of after the upload arrives and the server 409s. Then: the manifest's agent schemas against the live app row, every binding a deploy would push, aliases the source calls that nothing bound (queries, workflows AND agents), bindings this bundle stopped calling (the same transition — and the same baseline — `deploy` reports, so the two cannot disagree), capability-gated SDK calls the manifest doesn't declare, a missing icon/theme, a missing app `description` (it heads the capability catalog the chat agent reads every turn, and its absence has no other symptom), a `vite.config.ts` that never defines `global`/`__DEV__`, a `window.open` in the app's own source, and an INSTALLED `@lotics/app-sdk` below the version that understands the host's realtime push — read from `node_modules`, not the dependency range, because a caret is minor-locked below 1.0 so `^0.79.x` can never resolve `0.80` and `npm update` does nothing (all three fail ONLY in the deployed app — dev bundles with esbuild and production with rollup, so typecheck, lint, build and `app dev` are all green while react-native-web reads `global.cancelAnimationFrame` as a free variable and the sandboxed iframe drops a popup silently), an agent whose capability and its reach disagree, in EITHER direction, over any of the five declaration-bound tools (`run_app_query`/`run_app_workflow` against `query_aliases`/`workflow_aliases`; `grep_knowledge`/`read_knowledge`/`list_knowledge` against `knowledge_doc_ids`) — the tool is the capability, the list is the reach, and a tool with no reach means every call it makes is refused while the run still COMPLETES, so it surfaces as a model ignoring its prompt; read off the live row, never the manifest, which mirrors those fields but is pushed by no verb, and a notice for any alias the source computes at runtime (invisible to every check here and to `--prune`'s unbind guard). **And whether the kit this app builds against has fallen behind what is published** — `@lotics/ui` and `@lotics/app-sdk`, read from `node_modules` for the same reason as the floor check above: a range keeps accepting, so an app pinned `^44.x` reads healthy for a year, and even an in-range one sits on the lockfile's older patch until `npm update` (never `npm install`, which honours the lock). A MAJOR behind is loud and names the packages actually behind — plus `@lotics/ui`'s `MIGRATION.md`, when ui is one of them, since it is the only half that keeps one; anything smaller is one quiet line, because a warning that fires on every deploy is one the reader stops seeing. The registry lookup is bounded and every failure — offline, slow, private — is silence: a version check must never become a new way for a deploy to fail. Every deploy finding is the same helper `deploy` calls, so a green check means a deploy will not complain. **And the PORTABILITY gate, which is the one rule `check` runs that a deploy does not** — the ids an app cannot carry into another workspace, over the working tree, with the same exclusions the deploy tar applies. Two rules. **An id this workspace MINTED**, written into `src/`, a `.md` or the app's own docs — it resolves to nothing in a copy, and in prose it is an instruction the copier's agent follows; this is the one a `starter publish` also refuses, on the uploaded archive. **And an id-shaped STAND-IN** too short for the generator that mints its prefix (`"opt_X"`, `"fld_a"` — quoted or in a code span, so a bare `opt_in` stays legal, and never in a test file), which only `check` runs, and which additionally reads a workflow body and the manifest: those two are exempt from the first rule because a publish INVERTS a real id there, and it cannot invert a fake — so without this a stand-in survives until the publish resolves it against the app's footprint, on somebody else's machine. Each is reported as `<file>:<line> — <id>` with the one edit that fixes it. This gate reads only the files, but the command around it still needs a resolvable credential and the live app row, so it is not an offline check. **Exits 1 on that and on what a `deploy` would REFUSE or PUSH** — an agent schema that disagrees with the live app, and any binding the project has ahead of the app (an edited workflow body or declaration, edited agent prose, a changed query). Both are things a deploy would act on, so CI gating on a green check means a deploy has nothing left to do; genuine advisories (capabilities, branding, a runtime-computed alias, orphaned bindings) stay advisory and never fail it. |
 | `lotics app workflow set <alias>` | Push the edited `src/workflows/<alias>.ts` body through `set_app_workflow` (the single author of `apps.workflows`). Reads the body from disk (header + `/// <reference>` + `export {};` marker + the `__workflow` wrapper all stripped) + the typed `inputs`/`outputs` **and the `description`** from `package.json#lotics.workflows.<alias>`; the **server** re-verifies the body and echoes the bound `outputs` (declared, else DERIVED from `return({ data })`). The `description` is the one line an agent reads when choosing between the app's aliases (the workflow counterpart to a query's) — authored in the manifest so it lives beside the body in version control and rides every push; omit it and the workflow keeps whatever description it already has, so a push can never blank one set elsewhere. When the manifest declared NO `outputs`, the DERIVED echo is written back into `package.json#lotics.workflows.<alias>.outputs` (a SURGICAL write — preserves `knowledge`/`config` and every other manifest field) and that alias's types are refreshed in place, so `useWorkflow("<alias>")`'s `result.data` is typed immediately with no hand-copy and no second `lotics app codegen`; an explicitly-declared `outputs` is authoritative and never overwritten. Deploy still never authors workflows — this is a CLI convenience over the existing tool. Clear error + non-zero exit on a missing file, an alias absent from the manifest, or a verify failure. |
 | `lotics app agent set <alias>` | Push `src/agents/<alias>.md` — plus `inputs`/`outputs` when `package.json#lotics.agents.<alias>` declares them — through `set_app_agent`. The agent mirror of `app workflow set`, and the deploy-free authoring path for an agent's prose and its typed edges. **It sends only those fields.** Everything else is absent, and absent means unchanged, so a declaration this CLI does not model cannot be reverted by a push from a checkout that predates it — the chat authoring agent's `knowledge_doc_ids`, another operator's `query_aliases` grant. To change one of those, call `set_app_agent` with just that field (`lotics run set_app_agent '{"app_id":…,"alias":…,"tool_names":[…]}'` — it merges), then `app pull` to bring the manifest back in step. **CREATES the alias when the app has not bound one yet**, so a new agent is authored the same way a new workflow is: write the prose, declare the typed half, push. A create needs the prose file (an agent without instructions is not an agent); it is gated on nothing else, because what keeps a binding alive is a `useAppAgentRun("<alias>")` call site in the shipped bundle — a deploy prunes an agent the bundle never names, manifest entry or not. The prose push is a conditional write against the fingerprint this project last saw, so it is refused rather than allowed to overwrite prose someone else changed. Clear error + non-zero exit when there is no prose file and nothing declared to push instead, when a create has no prose to create from, or when the file is empty once the header is stripped. |
 | `lotics app query set <alias>` \| `--all` | Push `package.json#lotics.queries` (`{ ast, params? }` per alias) to `apps.queries` through `set_app_query` — **the only author of a query binding**, the mirror of `app workflow set`. A deploy pushes a DRIFTED declaration through this same verb before it ships (see `app deploy`), so this is the explicit single-alias path, not the only way a query reaches the app. The **server** validates each one exactly as it always did (alias identifier, workspace-only tables, resolvable fields, declared params). `--all` pushes every declared alias, alias-sorted, stopping at the first failure and naming what already landed. Clear error + non-zero exit on an alias absent from the manifest or a validation failure. **The declaration's fields MERGE**, so the manifest is not a snapshot: deleting `params` from an alias and pushing leaves the live params exactly where they were, because an absent key means "unchanged". Clear one with `params: null`, or replace the map with the set you want. |

package/docs/document_templates.md

@@ -86,8 +86,10 @@ format handles display.
 At generate time, `data` must provide a key for **every** marker — pass `""` for fields
 that should render blank; a missing key fails with the full list of missing markers.
 
-To add markers/loops/conditionals to the uploaded file from the CLI: `word_replace_text`,
-`word_insert_loop`, `word_insert_conditional` (and their `remove_*` counterparts).
+To read the uploaded file before marking it: `word_get_content`, `word_find_text`,
+`word_get_table_data`. To add markers/loops/conditionals: `word_replace_text`,
+`word_insert_loop`, `word_insert_conditional` — unmarking is `word_replace_text` putting the
+plain text back.
 
 ### Email (`create_email_template`)
 

package/docs/knowledge_docs.md

@@ -70,10 +70,10 @@ that member's agent.
 Docs are not injected wholesale. The agent works the corpus like a filesystem, and all three
 verbs respect access + activation, so only docs the caller may use ever surface.
 
-1. **`list_knowledge`** — `ls`. The corpus as a folder tree: name, id, folder, and a truncated
-   description. No bodies.
+1. **`list_knowledge`** — `ls`. The corpus as a flat list: id, name, tags, and a truncated
+   description; `tag` narrows it. No bodies.
 2. **`grep_knowledge`** — `grep -rn`. Match across every readable doc (or one doc, or one
-   folder), returning **doc, line number, and the matching line**. It runs inside Postgres,
+   tag), returning **doc, line number, and the matching line**. It runs inside Postgres,
    so only matching lines cross the wire.
 3. **`read_knowledge`** — `cat` / `sed -n 'X,Yp'`. Read a doc whole or by line range, to see
    the context around a hit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.183.0",
+  "version": "0.184.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {