@lotics/cli 0.321.89 → 0.321.91
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/src/cli.js +203 -181
- package/dist/src/client.js +1 -1
- package/docs/cli_reference.md +1 -0
- package/docs/data_model.md +1 -1
- package/docs/design.md +2 -0
- package/docs/working_in_a_workspace.md +1 -1
- package/package.json +1 -1
package/dist/src/client.js
CHANGED
|
@@ -78,7 +78,7 @@ function telemetryErrorMessage(status, parsed) {
|
|
|
78
78
|
|
|
79
79
|
// ../shared/src/cli_capabilities.ts
|
|
80
80
|
var CLI_CAPABILITIES_HEADER = "x-lotics-cli-capabilities";
|
|
81
|
-
var CLI_CAPABILITIES = ["docs-fallback"];
|
|
81
|
+
var CLI_CAPABILITIES = ["docs-fallback", "answer-file"];
|
|
82
82
|
|
|
83
83
|
// ../shared/src/proxy_upload_limit.ts
|
|
84
84
|
var PROXY_UPLOAD_MAX_BYTES = 100 * 1024 * 1024;
|
package/docs/cli_reference.md
CHANGED
|
@@ -31,6 +31,7 @@ Per-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. S
|
|
|
31
31
|
| — | **Every tool is invoked here, including the ones that RUN something** (`run_app_workflow`, `run_app_query`) and every one that builds: `set_tables` (a list of table documents), `set_app` (one app), `set_workflow`. A command exists only for work that touches a local file: `app apply`, `app create --custom`, `app pull`, `app deploy`. |
|
|
32
32
|
| — | **An app's queries and workflows take more than their params and inputs** (`lotics docs agent_surface`). `run_app_query '{"app_id","alias","params"}'` also takes `filters` and `sort` over the query's output columns, `fields` (the columns to return), `count` with `count_by` or `count_where`, `aggregate`, `limit` (200 rows at most; 50 where none is stated) and `cursor`, and `runs` — up to 20 reads in one call, each `{"alias", …}`, a refused one answered with its `error`; one call's rows total at most 262,144 bytes. `export: {"key", …narrowing}` instead of the read arguments makes the file an app's Export makes (`lotics docs agent_surface`). `run_app_workflow '{"app_id","alias","inputs"}'` also takes `dry_run: true` — a rehearsal on the real inputs, nothing written or sent; the answer is what the run would return, with the reads it made under `dry_run.reads`, the calls it would make under `dry_run.writes` and the papers it rendered under `dry_run.papers` and the parts of the answer it could not say under `dry_run.unpredicted`; a workflow no dry run is offered of answers `status: "not_previewed"` — and `runs` — up to 50 runs in order, the first refused, failed or not previewed ending the call, an input `{"from_run": <index>, "path": "data.<key>"}` reading an earlier run's answer. |
|
|
33
33
|
| — | **The exit code reports the WORK, not just the call — for the tool that RUNS one.** `run_app_workflow` whose envelope carries a failed `status` (`error`/`failed`/`cancelled`, or `not_previewed` — a dry run asked for and not given) 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` is data, and exits 0. |
|
|
34
|
+
| `lotics run <tool> '<json>'` with `as_file: true` | An answer that names its own file (`_file`) is saved as that file, whole JSON, where the command runs, or in `-o <dir>`; the path prints after the answer (on stderr under `--json`). The same call names the same file, so running it again replaces it. |
|
|
34
35
|
| `lotics run <tool> '<json>' -o <dir>` | Also save every **signed link** the answer carries — an object with a `url`, a `filename` and the `expires_at` its signature ends at, at any depth, such as `screenshot_app`'s images. Each is fetched into `<dir>` (created if missing) under its `filename`, taking a free spelling beside a file of that name already there, and a link's `snapshot` text is written beside it as `<name>.txt`. The written paths follow the answer on **stdout**, one per line (on stderr under `--json`, whose stdout stays the one object). A link is signed for an hour; one the store no longer serves exits non-zero. A workspace file states no `expires_at` and is left to `lotics file download`. |
|
|
35
36
|
| `lotics run set_members '{"members": {"<email or member id>": {"role": "member", "name": "…"}}}'` | Invite to this workspace (`name` is the name the invitation carries) or set a person's role in it (`role`: `member` or `admin`; `null` takes the person, or the invitation pending to that address, out of it); `groups` keeps the member groups in the same call. An admin of this workspace or an organization owner. Renaming or removing a person, restoring one, co-ownership and a member who signs in by a name are a person's in Settings → Members, and no tool takes them. The whole input is checked before an email is sent. A member's `lotics tools` lists neither `set_members` nor `set_workspace`. View-as is the web app's preview alone; the CLI acts as the signed-in member. |
|
|
36
37
|
| `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. |
|
package/docs/data_model.md
CHANGED
|
@@ -188,7 +188,7 @@ A table is named by its alias wherever a call names one (`table_id`, a link's `t
|
|
|
188
188
|
(a parent and its children).
|
|
189
189
|
A link already holding rows is paired the same way, with its partner stated beside it in the call: the partner is filled from
|
|
190
190
|
the links the rows hold and no cell of the link is rewritten. `pair: null` lets a pair go, both fields staying one-way links
|
|
191
|
-
with their values; a field that holds one row, the partner or the link itself, refuses a pair two rows would crowd, naming the rows.
|
|
191
|
+
with their values, and deleting one field of a pair leaves the other a one-way link; a field that holds one row, the partner or the link itself, refuses a pair two rows would crowd, naming the rows.
|
|
192
192
|
The partner may stand on a table the call does not name: `pair: "<alias>"` makes it there, or pairs the one-way link that table
|
|
193
193
|
already holds under that alias, and the answer lists that table among the call's. Only someone who manages that table may.
|
|
194
194
|
- A formula's `output_type` is inferred from its expression; state it only to override.
|
package/docs/design.md
CHANGED
|
@@ -418,6 +418,8 @@ admin edits the table. What a `workflow` or a paper did stands, so a way back th
|
|
|
418
418
|
|
|
419
419
|
#### Stages
|
|
420
420
|
|
|
421
|
+
Work the owner named no decider for has no status: the row saved is the fact (a goods receipt nobody approves moves
|
|
422
|
+
stock as it is saved), and a stage, its owner or an approval enters with the person the owner said decides.
|
|
421
423
|
Name each job's work plan by its shape: a status a person sets; a pipeline, where who holds the row and for how long
|
|
422
424
|
matter; or tasks, where only how many are done counts (`records.task`). A pipeline states each stage once in
|
|
423
425
|
`records.status.stages` — its `owner` (a member field, a link's member field, or `{ "group": <id> }`, a member group) and its target
|
|
@@ -60,7 +60,7 @@ A stored text is changed by `edits`, never sent whole again: `set_workflow` (wit
|
|
|
60
60
|
|
|
61
61
|
A long text not stored yet rides a file. `set_workflow` takes `source_file_id` in place of `source`, `set_knowledge` takes `content_file_id` in place of `content`, and `set_template` takes `template_file_id` in place of an html or email `template`: write the text where you work, upload it with `upload_file` (`files`), and pass the `file_id` the upload answers.
|
|
62
62
|
|
|
63
|
-
Many rows come as a file.
|
|
63
|
+
Many rows come as a file. `query_records` with `as_file: true` sends the page as a JSON file and lists no rows: over MCP an embedded file, on the CLI a file `lotics run` saves where it runs (or in `-o <dir>`) and names. The file is the answer whole: `records`, each with `record_id`, `data` and `display` keyed by field alias, so code reads every row. Without a `limit` it takes the page maximum of 1,000 rows; `has_more` and `offset` page past it.
|
|
64
64
|
|
|
65
65
|
Many rows go back as a file too. `create_records` and `update_records` take `rows_file_id`: a JSON file holding the call's per-row keys, in place of stating them. Everything else stays in the call: `table_id`, `dry_run`, `row_op`, `return_fields`.
|
|
66
66
|
|