@lotics/app-sdk 0.81.1 → 0.82.1

package/dist/src/comments.d.ts

@@ -1,8 +1,6 @@
 /** A file attached to a comment, in the resolved (serving) shape the list returns. */
 export interface AppCommentFile {
     id: string;
-    /** Storage key — needed to re-send the file when editing a comment. */
-    file_storage_key: string;
     filename: string;
     mime_type: string;
     url?: string;

package/dist/src/comments.js

@@ -32,14 +32,16 @@ import { useCallback } from "react";
 import useSWR from "swr";
 import { rpc } from "./rpc.js";
 import { useAppContext } from "./viewer.js";
-/** The reduced storage shape the update endpoint accepts for `files`. */
-function toStorageFiles(files) {
-    return (files ?? []).map((f) => ({
-        id: f.id,
-        file_storage_key: f.file_storage_key,
-        filename: f.filename,
-        mime_type: f.mime_type,
-    }));
+/**
+ * The attachment set as ids — what the update endpoint wants.
+ *
+ * Sending whole file objects instead would be a full-snapshot write of metadata
+ * this client does not own: a filename or a storage key echoed back from a read
+ * lands in the row verbatim, so a stale copy overwrites what is stored. An id
+ * the server resolves for itself cannot do that.
+ */
+function toFileIds(files) {
+    return (files ?? []).map((f) => f.id);
 }
 let optimisticCounter = 0;
 /**
@@ -122,7 +124,7 @@ export function useComments(args) {
                 record_id,
                 comment_id: id,
                 content,
-                files: toStorageFiles(currentFiles),
+                file_ids: toFileIds(currentFiles),
             });
             return rpc("comments.list", { record_id });
         }, {

package/docs/ai.md

@@ -322,6 +322,25 @@ Publish the **rendered** view, not the whole table. A screen that shows page 2 o
 
 Declarative and lifecycle-bound: mounting or changing `context` pushes it; unmounting, renaming the `slot`, or passing `null` clears it. Independent components hold **different slots** at once (a list screen + an open drawer), and the newest value per slot wins. Re-posting is change-gated — passing a fresh inline object each render does **not** spam the host; only a real value change re-publishes.
 
+### A slot that never publishes looks exactly like a slot with nothing to say
+
+The failure mode worth knowing before you wire one: this hook has **no visible output**. A
+`useAiContext` behind a guard that never opens publishes `null` forever while the screen it
+describes renders perfectly, and nothing anywhere reports it. Silence is the same shape as
+"there is nothing to report", so neither the app nor a review catches it.
+
+The usual cause is a guard on the query state. `useQuery`'s `error` is `string | null` — it is
+**never `undefined`** — so `error !== undefined` is always true and holds the guard shut on every
+render. Write `if (loading || error) return;`, which is correct whichever of the two the field
+turns out to be, and reads as the question you meant.
+
+**Verify by observing what is published, never by reading the code.** Run the app under
+`lotics app dev` and listen for the host notification on the wrapper page — the payload is the
+context as the chat agent will receive it. Check three things, because each fails differently:
+the slot carries REAL values matching what is on screen (not placeholders), it clears to `null`
+when the surface closes or the tab changes, and it does not publish while the first read is still
+in flight — a count of zero taken from a pending query is an answer nothing measured.
+
 ### The caps (host-enforced — exceeding them truncates or drops, never errors)
 
 | Field | Cap |

package/docs/members_and_options.md

@@ -279,8 +279,9 @@ updateComment, deleteComment, refetch }`.
 - `comments` — newest first on the wire (server order). Pass the array as-is to `@lotics/ui`'s
   `CommentList`, which re-sorts oldest-first for display. Each `AppComment`: `{ id, record_id,
   table_id, member_id, content, files, workspace_id, created_at, updated_at }`. Attachments
-  (`AppCommentFile`) carry `id` / `filename` / `mime_type` plus `file_storage_key` (needed when
-  re-sending files on edit). The `url` / `thumbnail_url` / `preview_url` fields exist on the type
+  (`AppCommentFile`) carry `id` / `filename` / `mime_type` — a file's identity is its `id`, and
+  the server re-reads every attachment from storage by that id, so nothing else you hold about a
+  file can affect what is stored. The `url` / `thumbnail_url` / `preview_url` fields exist on the type
   but the server does not populate them today — render attachments by name and type (what
   `CommentList`'s default file row does), never by counting on a fetchable URL.
 - `createComment({ content, file_ids? })` — posts as the viewing member. `file_ids` come from

package/package.json

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