@lotics/cli 0.284.0 → 0.284.1

package/docs/field_values.md

@@ -0,0 +1,33 @@
+# Field values — what a write takes for each field type
+
+The value `create_records` and `update_records` take for a field.
+
+## Values by type
+
+| Type | Value |
+|---|---|
+| `text` | `"hello"` |
+| `number` | `42` |
+| `boolean` | `true` |
+| `date` | `"2025-03-14"`, or a month `"2025-03"` or a year `"2025"`, stored as written and compared as its first day |
+| `datetime` | a `date` of this format: `"2025-03-14T09:00"`, never a month or a year |
+| `date_range` | a `date` of this format: `"2025-03-01/2025-03-15"`, both halves full dates |
+| `datetime_range` | a `date` of this format: `"2025-03-01T09:00/2025-03-15T17:00"`, both halves full |
+| `select` | `["opt_…"]` |
+| `select_member` | `["mbr_…"]` |
+| `select_record_link` | `["rec_…"]` |
+| `files` | `["fil_…"]`, ids of uploaded files |
+| `formula`, `rollup`, `lookup`, `autonumber`, a `date` with `derive_from` | none — the platform writes them, and a write naming one is refused |
+
+## Lists
+
+`select`, `select_member`, `select_record_link` and `files` store an ARRAY, even where the field holds
+one value.
+
+- A single-select is a ONE-element array; a bare `"opt_…"` is accepted and wrapped. A single
+  `select_member` takes a bare `"mbr_…"` the same way.
+- `select_record_link` and `files` take an array only.
+- Two options on a single-select, or two members on a single `select_member`, are refused.
+- `update_records`' `add_to`, `remove_from` and `replace` take arrays of the same items: `opt_` keys
+  for a select, member ids for a `select_member`, record ids for a `select_record_link`, file ids for
+  `files`.

package/docs/knowledge_docs.md

@@ -52,7 +52,7 @@ surface, not this tool.
 ## Access
 
 A knowledge doc reaches an agent only when the member can `use` the doc. New docs are private
-to the owner; share them with other members or groups using the IAM tool `share_resource`
+to the owner; share them with other members or groups using the IAM tool `share_resource` on the CLI or in chat
 (category **Admin**; `unshare_resource` to revoke). An organization admin who is a person is no
 exception: they read a doc only once it is shared with them, or once they share it with
 themselves, which the audit log records. An API key acting as itself keeps the access set on the
@@ -117,7 +117,7 @@ pattern that was never too broad.
   with the reason.
 
 Where an expression cannot express the question at all — a value that must be computed, a
-layout matching cannot address — stage the doc into a code run instead (`code_exec` with
+layout matching cannot address — stage the doc into a code run instead (`code_exec`, in chat or an app agent, with
 `knowledge_doc_ids` puts it at `inputs/knowledge/<id>.md` as a real file).
 
 ### What a result is bounded by
@@ -224,8 +224,8 @@ lotics tools update_knowledge           # full input schema for any knowledge to
 
 The Knowledge category covers `list_knowledge`, `create_knowledge`, `update_knowledge`, and
 `delete_knowledge` — fronted by the `lotics knowledge list | create | get | update | tag | hide |
-unhide | rm` commands, and reachable over MCP as well, so a corpus can be authored from whichever
-surface you already work in. `list`, `tag`, `hide` and `unhide` go over REST rather than a tool, because
+unhide | rm` commands, and all but `delete_knowledge` reachable over MCP as well, so a corpus can be
+authored from whichever surface you already work in. `list`, `tag`, `hide` and `unhide` go over REST rather than a tool, because
 they are a person's view of the corpus: the tools answer what the ASSISTANT may browse, and a
-hidden doc is out of that set by definition. Sharing a doc to other members is `share_resource` / `unshare_resource` (category
-**Admin**).
+hidden doc is out of that set by definition. Sharing a doc to other members is `share_resource` / `unshare_resource` on the
+CLI or in chat (category **Admin**).

package/docs/migration.md

@@ -21,7 +21,7 @@ templates and roles are the workspace's own.
 | `lotics scaffold diff` | `lotics model apply <model.json> --plan` — what the apply would change, writing nothing |
 | `lotics scaffold export` | `lotics model pull [-o <model.json>]` — the workspace's model, rebuilt from what owns each part |
 | `lotics app pull`, `app codegen`, `app check`, `app dev`, `app preview` | nothing local: read an app with `lotics run get_app`, and change it through its tools |
-| `lotics app workflow set` / `app query set` / `app agent set` | `lotics run set_app_workflow` / `set_app_query` / `set_app_agent` — each mints a version |
+| `lotics app workflow set` / `app query set` / `app agent set` | `lotics run set_app_workflow` / `set_app_queries` / `set_app_agent` — each mints a version |
 | `lotics app versions` + a redeploy of an old tree | `lotics run query_app_versions`, then `lotics run rollback_app` — restores the app's earlier version; table changes and data writes stay |
 | `lotics app rename`, `app subdomain`, `package.json#lotics.capabilities` | `lotics run update_app` (`name`, `public_subdomain`, `capabilities`) |
 | `lotics app api publish` / `unpublish` | `lotics run publish_app_api` / `unpublish_app_api` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.284.0",
+  "version": "0.284.1",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {
@@ -20,6 +20,7 @@
     "build:binaries": "node scripts/build_binaries.mjs",
     "publish:binaries": "node scripts/build_binaries.mjs && node scripts/publish_binaries.mjs",
     "generate:model-reference": "node --import tsx dev/model_reference_gen.ts",
+    "generate:examples": "node --import tsx dev/examples_gen.ts",
     "generate:snapshots": "node --import tsx dev/factory_snapshots.ts",
     "typecheck": "tsgo --noEmit",
     "lint": "oxlint",