@lotics/cli 0.316.15 → 0.316.17

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 model` · `lotics docs model/<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; 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 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. |

package/README.md

@@ -14,7 +14,7 @@ Lotics is an AI-powered operations platform. Through this CLI you can:
 
 **`lotics docs`** lists this CLI's references, carried inside it — the model reference and every
 doc below — so a doc always describes the binary answering. `lotics docs <area>` prints one
-(`lotics docs model`). Every answer is capped at a page, so a long doc hands back its section list
+(`lotics docs reference`). Every answer is capped at a page, so a long doc hands back its section list
 and `lotics docs <area>/<section>`. A page the CLI's copy lacks — one the server added since, which
 an error can cite — is read from the server, and `lotics docs [<area>] --grep <text>` searches the
 references the server serves; both use this machine's credential. A custom-code app's SDK reference
@@ -75,7 +75,7 @@ files of several trades are listed at `https://lotics.ai/presets/index.json` (ea
 words, and pass its tables to `set_tables`.
 
 ```bash
-lotics docs model                          # the keys, with a worked example
+lotics docs reference                          # the keys, with a worked example
 lotics run set_tables @tables.json          # every table of the workspace, in one call
 lotics app apply orders.app.json --check   # set_app as a dry run: everything wrong, nothing written
 lotics app apply orders.app.json           # set_app: creates the app, or edits the one the file records