@lotics/app-sdk 0.74.0 → 0.75.1

package/docs/ai.md

@@ -216,6 +216,17 @@ Sessions are scoped to the authenticated member who ran them: two members using
 
 Every file in a `multi` input is materialized — nothing is collapsed to the first. Get the ids from [`useFileUpload` / `useAttachments`](./files.md).
 
+**So do not dispatch on the file type.** Every tier above reads, which means the format tells you
+nothing about what a document IS — the same claim form arrives as `.xlsx` from a laptop, as a PDF
+through a chat app, and as a photo of a printout; an invoice arrives as PDF, as the XML beside it,
+or as a screenshot. An intake that routes on the extension is reading the envelope, and it fails
+SILENTLY: the wrong extractor runs, returns something correctly shaped, and the user is handed a
+confident wrong answer. Let one agent read the drop and say what each document is, keyed on what
+only the content carries. Prefer separate output slots (`don_hang`, `hoa_don`, plus a named
+`bo_qua` for what fits neither) over a `loai` discriminator beside a payload — which slot a
+document lands in IS the classification, so there is no second field free to disagree with it, and
+nothing disappears quietly.
+
 **Why no tool:** the content ends up in the agent's context either way, so making it fetch what the server already holds costs a model round-trip and buys nothing. It also keeps the capability boundary tight — an agent that reads its own input never gains the ability to read *other* files in the workspace.
 
 **When to add a tool anyway.** Only to reach *past* what was inlined. A spreadsheet is materialized at 100 rows × 50 columns per sheet and a Word file at 1,000 elements; overflow is reported, never silent. If the agent must read row 4,000 of a large sheet, add `excel_get_range` / `excel_find_cells` (or `view_files` for an ad-hoc second look at a different file).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.74.0",
+  "version": "0.75.1",
   "description": "Runtime SDK for Lotics custom-code apps — typed hooks, postMessage bridge, mount entry point",
   "type": "module",
   "exports": {
@@ -45,7 +45,7 @@
     "@types/react-dom": "^19.0.0",
     "react": "19.2.3",
     "react-dom": "19.2.3",
-    "react-router": "7.18.1"
+    "react-router": "7.18.2"
   },
   "keywords": [
     "lotics",