@lotics/app-sdk 0.122.2 → 0.122.3

package/docs/ai.md

@@ -358,7 +358,7 @@ workflows (run_app_workflow):
 `?` 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. Both tools
-take an opaque inputs object, so this listing is the only place any of it is
+take an opaque object (a query's `params`, a workflow's `inputs`), so this listing is the only place any of it is
 legible.
 
 The app's own `description` heads that listing as `about:`, on both surfaces. It

package/docs/data_fetching.md

@@ -369,7 +369,7 @@ Wire shapes per output column type:
 | Column type | Cell value on the wire |
 |---|---|
 | `text` | `string` |
-| `number` | `number` (numeric database strings are normalized server-side; a rare decimal too precise for float64 stays a string — `row.num` parses both) |
+| `number` | `number` (numeric database strings are normalized server-side; a decimal with more digits than a double holds rounds to the double) |
 | `boolean` | `boolean` |
 | `date` | `"YYYY-MM-DD"` — a calendar day, no time component (a reduced-precision date field may also carry `"YYYY-MM"` or `"YYYY"`; see below) |
 | `datetime` | `"YYYY-MM-DDTHH:mm"` — workspace wall-clock, minute precision |

package/docs/members_and_options.md

@@ -424,7 +424,7 @@ const { reverted, kept } = await undoRecordChange("job", recordId, entry.id);
   the call arrives, on a row their own row rule covers, and the record's lock, the table's checks
   and its write rules answer as for any save of theirs. `undoable` is `false`, and the call
   refused, for the entry that made the record, an entry that is an undo, one already put back, and
-  a viewer who may not write the record.
+  a viewer who may not write the record; a record in the trash is refused until it is restored.
   The undo is an entry of its own; the answer arrives once the record's reads are read anew.
 - **Pages**: newest first, about thirty entries each; `next` is where the trail goes on —
   `undefined` at its end. A page may hold fewer entries and still say `next` where the trail it read

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.122.2",
+  "version": "0.122.3",
   "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": {