@lotics/app-sdk 0.87.8 → 0.87.9

package/docs/mutations.md

@@ -153,8 +153,7 @@ envelope's grammar — `message` is required, `field_errors` never reaches the a
   against those. So a producer — a workflow's `return({ data })`, an app agent's
   `submit_result` — is handed the legal keys and cannot settle a label where a key belongs.
   Prefer `field` for any select backed by a real field (the generated type tracks it, no
-  redeploy); use inline `options` for a fixed enum the app owns or a select you plan to
-  **package** (a `field` form carries a concrete field id and can't ride a package contract).
+  redeploy); use inline `options` for a fixed enum the app owns.
 - **Validated at run.** On a success return, the returned `data` is validated against the
   schema at the app boundary — a mismatch resolves as `status: "error"` with a field-level
   message, so a declared output is a real contract. An *error* return's `data` passes through
@@ -251,10 +250,8 @@ When the alias declares `inputs`, the server validates the payload before the wo
   (`lotics app workflow set` / `set_app_workflow`; `lotics app deploy` never binds workflows) with
   `select input references field "<key>", which does not exist in this workspace` /
   `… which is a <type> field, not a select`. Prefer `field` for any select backed by a real
-  field; keep `options` for a fixed enum the app owns or a select you plan to **package** — a
-  `field`-form select can't ride a package contract (it carries a concrete field id), so inline
-  the options before publishing. Populate pickers from `useFieldOptions` either way (the live
-  option set — see [members_and_options](./members_and_options.md)).
+  field; keep `options` for a fixed enum the app owns. Populate pickers from `useFieldOptions`
+  either way (the live option set — see [members_and_options](./members_and_options.md)).
 
 If the alias declares **no** `inputs`, the payload passes through opaquely — no validation,
 no typing, no reference binding. Fine for a zero-input action; declare inputs for anything

package/docs/runtime.md

@@ -24,7 +24,7 @@ mount(<App />);
 `dist/src/mount.d.ts`) is called **once** from the app's entry file. It:
 
 1. **Registers the mock fixture**, if `options.fixture` was passed (below).
-2. **Finds or creates `#root`.** Uses the `<div id="root">` from the starter's
+2. **Finds or creates `#root`.** Uses the `<div id="root">` from the scaffold's
    `index.html`; if the bundler didn't ship one, it creates and appends it.
 3. **Installs visible error handlers.** `window` `error` and
    `unhandledrejection` listeners render a fixed red monospace banner (message +
@@ -179,7 +179,7 @@ surfaces:
 
 | Op | Embedded (product) | `lotics app dev` | Standalone |
 |---|---|---|---|
-| `query`, `field_options`, `workflow`, `members`, `context`, `binding`, `upload`, `urlState.get/set`, `openExternal` | yes | yes | yes |
+| `query`, `field_options`, `workflow`, `members`, `context`, `upload`, `urlState.get/set`, `openExternal` | yes | yes | yes |
 | `comments.*` | yes | yes | rejects — `"Comments are available only in embedded apps — a signed-in member is required."` |
 | `agentRun` (streaming, internal to `useAgentRun`) | yes | yes | yes |
 | `agentRun.get`, `agentRun.cancel` | yes | **no** — the dev forwarder doesn't implement them (`"Unknown RPC op: …"`) | yes |

package/package.json

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