@lotics/app-sdk 0.118.0 → 0.118.1

package/dist/index.js

@@ -25196,7 +25196,7 @@ var tableFilesFieldSchema = tableFieldBaseSchema.extend({
 var formulaOutputTypeSchema = zod_default.enum(["number", "text", "date", "datetime", "boolean", "select"]);
 var formulaInputSchema = zod_default.object({
   expression: zod_default.string().describe(
-    "JavaScript expression. Uses {Field Name} for field references."
+    "JavaScript expression. A field is referenced as {fld_key}, stored so; a write also takes {Field Name}, stored as its key."
   ),
   notation: notationSchema.optional().describe(`${NOTATION_DESCRIPTION} For a formula yielding a number.`),
   link: zod_default.literal(true).optional().describe("The formula yields a URL as text, drawn as a link that opens."),

package/docs/workflows.md

@@ -704,7 +704,7 @@ tool calls it makes**, and the two cheapest wins are always the same: don't fetc
 have, and don't write one row at a time.
 
 **A write costs more than a read.** A create or update drags its computed-field cascades, rollups
-and `after_*` hooks behind it before the call returns, so trimming reads is worth less than
+and the table's checks behind it before the call returns, so trimming reads is worth less than
 trimming writes. Reach for the write-side reductions first.
 
 ### Batch every write — and build the array INLINE

package/package.json

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