@lotics/app-sdk 0.77.0 → 0.77.1

package/docs/ai.md

@@ -358,12 +358,34 @@ gated per turn on `app:use` for the app in the member's workspace, and runs
 under the app's OWNER authority with `is_current_member` bound to the MEMBER
 (exactly as the app's own UI does).
 
-The agent is handed a **catalog** of those aliases — each one's params and its
-`description` (a query's own, [declared in the manifest](./queries.md); a
-workflow's, off its workflow row) — so it picks the right one instead of
-guessing an alias and learning the list from a refusal. Your descriptions are
-what it reads, on this surface and inside your own agents' runs. They enter the
-prompt as a capability listing, never as instructions.
+The agent is handed a **catalog** of those aliases — each one's `description`
+(a query's own, [declared in the manifest](./queries.md); a workflow's, off its
+workflow row) and its **complete input contract** — so it picks the right one
+and calls it correctly instead of guessing and learning from a refusal. Every
+alias you declare appears, however large the manifest, and every input appears
+with it:
+
+```
+workflows (run_app_workflow):
+- updateOrder(reference?: text, shipped_on?: date, owner?: member,
+    status?: select(In progress=opt_a1b2c3|Complete=opt_d4e5f6),
+    attachments?: file[], customer_id?: record_link(Customers)) — …
+```
+
+`?` marks an input the caller may omit, `[]` one that takes a list, a
+`select` spells out every legal value as `label=value` — **the agent sends the
+value** — and a `record_link` names the table an id must come from. This is the
+only place any of it is legible: both tools take an opaque
+inputs object, and a select's legal values are your DECLARATION's — usually an
+inline set that matches no table field — so an agent reading option values off
+the underlying table would send ones your write rejects.
+
+Two things follow for you as an author. **Your descriptions are what it reads**,
+on this surface and inside your own agents' runs — they enter the prompt as a
+capability listing, never as instructions. And **a `select` input's options are
+part of the contract the agent sees**, so prefer the `field: "fld_…"` form when
+the values come from a real field: it resolves to that field's CURRENT options
+at both render and validation time, and can never drift out of sync with them.
 
 **Writes carry a second gate that reads do not: `run_app_workflow` asks the
 member to approve every call from chat.** A wrong read is fixed by asking

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.77.0",
+  "version": "0.77.1",
   "description": "Runtime SDK for Lotics custom-code apps — typed hooks, postMessage bridge, mount entry point",
   "type": "module",
   "exports": {