@lotics/app-sdk 0.51.1 → 0.51.2

package/dist/src/config.d.ts

@@ -1,7 +1,7 @@
 import type { AppConfigValue } from "./rpc.js";
 /**
  * Read the installation's customization config — the first rung of the App
- * Packages customization ladder (see docs/app_packages.md § The customization
+ * Packages customization ladder (see docs/packages.md § The customization
  * ladder). A package declares typed config knobs with defaults (labels, feature
  * toggles, theme, column choices); each installation stores the customized values
  * and the app reads them here. Updates flow: editing config in the product

package/dist/src/config.js

@@ -2,7 +2,7 @@ import { useMemo } from "react";
 import { useAppContext } from "./viewer.js";
 /**
  * Read the installation's customization config — the first rung of the App
- * Packages customization ladder (see docs/app_packages.md § The customization
+ * Packages customization ladder (see docs/packages.md § The customization
  * ladder). A package declares typed config knobs with defaults (labels, feature
  * toggles, theme, column choices); each installation stores the customized values
  * and the app reads them here. Updates flow: editing config in the product

package/docs/ai.md

@@ -176,7 +176,7 @@ Opens the Lotics messenger on a **fresh chat**, seeded with the given payload. T
 | `prompt` | **Prefills the chat composer.** The user sees it, can edit it, and sends it themselves — **nothing runs until they press send** |
 | `file_ids` | Files to attach (ids from [`readFiles(cell)`](./files.md) or an upload). The host resolves each id itself and attaches the current version; a **single** file also opens in a preview pane beside the chat |
 | `record_ids` | Records the chat should know about (ids from query rows). The host resolves them to table context — the agent can then read and act on them **under the signed-in member's authority** |
-| `context` | Free-text grounding ("Order ORD-2481, customer Acme…"). The host stamps the app's identity (id + name) alongside it automatically |
+| `context` | Free-text grounding ("Order ORD-2481, customer Acme…"). The host stamps the app's identity (id + name) alongside it automatically. **User-visible verbatim**: the chat shows it as a context pill the user can expand (and dismiss before sending) — write it as user-readable prose, never internal jargon or anything sensitive |
 
 At least one of the four is required — an empty call rejects. The bridge carries only ids and text; the host resolves everything as the signed-in member, so the handoff can only surface what that member could already open. An unresolvable file or record is dropped with a visible toast and the rest of the handoff proceeds.
 

package/docs/runtime.md

@@ -408,11 +408,12 @@ contract aliases (`"tasks.title"`, `"tasks.status:to_do"`, role alias) with this
 workspace's `fld_`/`opt_`/`grp_` ids as values. Exact signature:
 `dist/src/rpc.d.ts`.
 
-You normally never call it yourself: the package project's generated
-`.lotics/app_fields.ts` (written by `lotics package new/extract/dev/sync` from
-`contract.json`) calls it once at **module load** via top-level await and
-exports plain-string `F` / `OPT` / `ROLE` maps — the same import surface as a
-bespoke app's baked codegen, but resolved per-installation at runtime:
+You normally never call it yourself: on a package installation (a published
+origin, or an install of someone's package) `lotics app codegen` emits a
+binding-form `.lotics/app_fields.ts` that calls it once at **module load** via
+top-level await and exports plain-string `F` / `OPT` / `ROLE` maps — the same
+import surface as a bespoke app's baked codegen, but resolved per-installation
+at runtime:
 
 ```ts
 import { OPT } from "../.lotics/app_fields";
@@ -426,16 +427,16 @@ const STATUS_DONE = OPT.TASKS.status.done; // this installation's "opt_…"
   never cached — a module-load failure rejects the whole graph (blank frame),
   so the fetch absorbs blips rather than bricking the boot on one lost request.
 - **Requires the starter's `build.target: "es2022"`** (top-level await does not
-  exist below it). `lotics package extract` refreshes `vite.config.ts` from the
-  current starter for exactly this reason.
+  exist below it). An app scaffolded before the starter set that target must
+  set it in `vite.config.ts` before shipping the binding form.
 - **Fails loud.** A key missing from the binding throws at boot with the alias
   named — the binding is verified complete at install/adopt, so a miss means
   the generated file is stale relative to the installed contract version
   (re-run the codegen, republish).
-- **Bespoke apps 404.** A never-adopted app has no binding; bespoke projects
-  keep the baked `lotics app codegen` variant instead. Shared code should not
-  call this directly — import from `.lotics/app_fields` and let the project
-  kind pick the implementation.
+- **Bespoke apps 404.** An app that is not a package installation has no
+  binding; codegen emits the baked variant for it instead. Shared code should
+  not call this directly — import from `.lotics/app_fields` and let codegen
+  pick the form.
 
 ## For package contributors
 

package/package.json

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