@lotics/app-sdk 0.123.5 → 0.123.6

package/docs/ai.md

@@ -336,11 +336,11 @@ This hook is a **one-way push of data the app already showed this member**. (Cha
 
 ### The chat can also USE the app, not just be told about it
 
-While a member has an app open, their chat agent can also **call that app's own
-declared aliases** — named queries via `run_app_query`, workflows via
+A member's chat agent can also **call the declared aliases of any app that member
+can use** (the open app when a call names none): named queries via `run_app_query`, workflows via
 `run_app_workflow`. This adds no exposure: every declared alias is already
 callable by that member ([the devtools test](./security.md#the-devtools-test)).
-It is gated per turn on `app:use`, and runs under the app's OWNER authority with
+It is gated on `app:use` when the call is made, 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 `description`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.123.5",
+  "version": "0.123.6",
   "description": "The SDK a Lotics custom-code app reads and writes through — typed hooks over the host bridge, cell readers, mount() and AppRouter",
   "type": "module",
   "exports": {