@lotics/cli 0.316.20 → 0.316.22

package/AGENTS.md

@@ -8,7 +8,7 @@ conventions are, and where the traps are.
 | `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>[/<section>]` · `lotics docs [<area>] --grep <text>` | This CLI's references, carried inside it so each describes the binary answering. Capped at a page: a doc that does not fit hands back its opening and the addresses into it, so the next call is smaller than the last. A page the copy lacks — one the server added since this binary was built, which a refusal can cite — is read from the server's `docs` tool with this machine's credential, and so is every `--grep`, over the references the server serves. A custom-code app's SDK reference is `node_modules/@lotics/app-sdk/AGENTS.md` inside the app. |
-| `lotics docs reference` · `lotics docs reference/<section>` | The keys of a table document and the components of an app tree: a table's fields keyed by alias, how a row of each table is recognised (`records`), and the apps stated over them. Every key, every field type with the config it needs, the rules, and a worked example; example files of several trades are listed at `https://lotics.ai/presets/index.json` — read one and pass its tables to `set_tables`. |
+| `lotics docs reference` · `lotics docs reference/<section>` | The keys of a table document and the components of an app tree: a table's fields keyed by alias, how a row of each table is recognised (`records`), and the apps stated over them. Every key, every field type with the config it needs, the rules, and a worked example. |
 | `lotics docs design` · `lotics docs design/<section>` | Designing an app — the treatment each kind of row takes with the `model` page stating its keys, the visual bar, and looking at what a write built. Opens on the common treatments; a finding names its section. |
 | `lotics docs examples` · `lotics docs examples/<treatment>` | Each treatment worked through in an app of a complete workspace: the job, the props to read, where it is the wrong one, and the excerpt. |
 | [docs/getting_started.md](./docs/getting_started.md) | What a workspace holds, and the one page to open for each job: building a workspace, changing an app, a rule on a table, a document, data and questions, a connected service, sharing. The first page an agent outside the product reads. |
@@ -95,7 +95,7 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
   agent-readable summary to the full structured object.
 - **Every tool is invoked one way — `lotics run <tool>`.** Including the ones that RUN something
   (`run_app_workflow`, `run_app_query`) and every one that builds
-  (`set_tables`, `set_app`, `set_app_queries`, `set_app_workflow`). A command
+  (`set_tables`, `set_app`, `set_app_queries`, `set_workflow`). A command
   exists only for work that touches a local file.
 - **Building is two tools, each a writer that creates without an id and edits with one.** `set_tables`
   takes `{ "tables": [...] }` — always a list, one or many, all or nothing — each table a document keyed
@@ -107,10 +107,9 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
   to change a node, refused with `base_version_id` when the app has moved past the version you read. `dry_run` checks
   without writing, a refusal lists everything wrong in the call, and every answer states the permissions the write
   granted and removed. The answer notes the treatments an author leaves unstated; nothing is written into the tree for them. A new workspace: one `set_tables` call with
-  the tables, then every `set_app` call, then fixes. The example files under `https://lotics.ai/presets/index.json` are read and their tables passed to
-  `set_tables`.
+  the tables, then every `set_app` call, then fixes.
 - **Every change to an app mints a version of it, and applying the earlier tree again is the undo.** An apply, a
-  deploy, a single `set_app_*` or `remove_app_binding`: each is a new version. Applying the earlier tree again restores the app — never a table change or a row a workflow wrote,
+  deploy, a single `set_app_*`: each is a new version. Applying the earlier tree again restores the app — never a table change or a row a workflow wrote,
   so try a write on a throwaway record.
 - **Exit codes are assertable, and they report the WORK rather than the call.** `lotics run` exits
   non-zero when a `run_app_workflow` result's own envelope carries a failed

package/README.md

@@ -69,10 +69,7 @@ both tables. A table is edited by an RFC 7396 merge patch of its document, where
 given no id and edit when given one, and `dry_run` checks without writing. Every answer states the permissions the
 write granted and removed.
 
-A new workspace: one `set_tables` call with the tables (at most 50, 200 first rows each, a call), then every `set_app` call, then fixes. Example
-files of several trades are listed at `https://lotics.ai/presets/index.json` (each at
-`https://lotics.ai/presets/<slug>.json`) — read the closest one, write your own in your business's
-words, and pass its tables to `set_tables`.
+A new workspace: one `set_tables` call with the tables (at most 50, 200 first rows each, a call), then every `set_app` call, then fixes.
 
 ```bash
 lotics docs reference                          # the keys, with a worked example
@@ -203,7 +200,7 @@ Unset, nothing is stored, nothing is sent, and no spool file is created.
 ### Reporting a problem
 
 ```bash
-lotics report '{"goal":"rename a view","actual":"no command does it","wanted":"lotics run update_view"}'
+lotics report '{"goal":"rename a view","actual":"no command does it","wanted":"lotics run set_tables"}'
 lotics report @report.json       # a long one, from a file
 cat report.json | lotics report -   # or from stdin — `-` is required, see below
 lotics report                    # the frame, and what is worth reporting
@@ -280,7 +277,6 @@ lotics download <file_id> -o ./reports/
 
 # What is in the store, newest first — one page, with the command for the next one
 lotics file list --limit 50
-lotics file delete <file_id>          # refused while anything still references it
 
 # CI / non-interactive (key inline)
 LOTICS_API_KEY=ltk_... lotics run get_workspace '{}'
@@ -318,7 +314,7 @@ lotics app pull                            # in the project: bring it up to the
 
 # What the app reads and writes is bound on the app, and each change mints a version:
 lotics run set_app_queries '{"app_id":"app_...","queries":{"openInvoices":{...}}}'
-lotics run set_app_workflow '{"app_id":"app_...","alias":"issueInvoice","source":"..."}'
+lotics run set_workflow '{"source":"on({ type: \"app\", app_id: \"app_...\", alias: \"issueInvoice\" });\n..."}'
 
 # Running an app's alias is a TOOL call, like every other tool. Exits non-zero
 # when the RUN failed, not only when the call did.