@lotics/app-sdk 0.98.3 → 0.98.5

package/dist/src/hooks.js

@@ -227,8 +227,9 @@ export function useInfiniteQuery(alias, params, opts) {
     // Keyset (seek) pagination: each page seeks past the previous page's
     // `next_cursor` instead of an increasing OFFSET, so deep scrolls stay O(page)
     // and never skip/duplicate a row as the set shifts. The cursor is opaque; the
-    // server keysets a sortable key (or the id default) and falls back to offset
-    // transparently. `loadMore`/`rows` are unchanged — the cursor is internal.
+    // server keysets a sortable key (the query's own order when `sort` is unset,
+    // else the id) and falls back to offset transparently. `loadMore`/`rows` are
+    // unchanged — the cursor is internal.
     const getKey = (index, prev) => {
         if (mockRows || !enabled)
             return null;

package/docs/data_fetching.md

@@ -241,8 +241,9 @@ Reads paginate two different ways, and the difference is load-bearing:
   opaque cursor instead of counting an offset, so a deep scroll stays O(page) and — the reason it
   matters — **never skips or duplicates a row as the set shifts** under concurrent inserts/deletes.
   The cursor is internal: the hook sends it and reads the next one back; you never see it. The
-  server keysets a single sortable key (the runtime `sort`, or the record-id default) and falls
-  back to offset transparently for a multi-key sort it can't seek. So an infinite feed needs **no
+  server keysets a single sortable key (the runtime `sort`, else the template's own order on a
+  column it projects, else the record id) and falls back to offset transparently for a multi-key
+  sort it can't seek. So an infinite feed needs **no
   dedupe** — key rows by `__source_record_id` for stable React keys, not to guard against repeats.
 - **`useQuery`, `usePaginatedQuery`, and manual `rpc("query", { limit, offset })` use offset
   pagination** — count `offset` rows, skip them, return the next page. Two consequences a keyset

package/docs/members_and_options.md

@@ -265,7 +265,7 @@ client-side up front, and re-checked server-side.
 - **The author is always the real signed-in member** — correct attribution, enforced server-side.
   **Warning:** under "View as", comments still author as the real member (the admin), not the
   view-as target — unlike `useViewer` and `is_current_member` scoping, which follow the target.
-- **Edit and delete are author-only**, checked server-side against the viewer. `EntryList`'s
+- **Edit and delete are author-only**, checked server-side against the viewer. `Timeline`'s
   `currentMemberId` prop drives the matching affordance client-side.
 
 ### Reading & writing
@@ -286,13 +286,13 @@ renders the panel. State: `{ comments, loading, error, available, createComment,
 updateComment, deleteComment, refetch }`.
 
 - `comments` — newest first on the wire (server order). Pass the array as-is to `@lotics/ui`'s
-  `EntryList`, which re-sorts oldest-first for display. Each `AppComment`: `{ id, record_id,
+  `Timeline`, which re-sorts oldest-first for display. Each `AppComment`: `{ id, record_id,
   table_id, member_id, author, content, files, workspace_id, created_at, updated_at }`. Attachments
   (`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
-  `EntryList`'s default file row does), never by counting on a fetchable URL.
+  `Timeline`'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
   `useFileUpload` / `useAttachments` (see [files](./files.md)). A comment must have content or at
   least one file (empty input is a client no-op; the server enforces the same rule). Content max
@@ -308,7 +308,7 @@ updateComment, deleteComment, refetch }`.
   app by someone the record references nowhere. So a thread that crosses a role boundary is legible without the app declaring member
   access it does not otherwise need, and a per-viewer app never widens its reach for a display
   string. `name` is `null` when the id no longer resolves in the org (a removed member) — render a
-  fallback (`EntryList` has an `unknownMember` label for exactly this). The one comment with no
+  fallback (`Timeline` has an `unknownMember` label for exactly this). The one comment with no
   `author` is the optimistic row `createComment` renders locally: the SDK knows the viewer's id and
   not their name, and it will not invent one. The server's row replaces it when the refetch lands.
 - **Freshness:** SWR-cached, revalidates on focus/reconnect, so another viewer's comment appears on
@@ -336,7 +336,7 @@ directly (full props: `node_modules/@lotics/ui/AGENTS.md` and its `docs/`):
 | A select value (stored or picker option) | `Status` | A `useFieldOptions` option, or `byKey(readSelect(cell)[0]?.key)`; accepts a single option, an array (multi → one badge each), or null (renders nothing). Missing/unknown color → neutral. |
 | A person, inline | `MemberChip` | `name` / `image` from a roster or a cell — both carry it; no image → initials |
 | A member picker | `MemberSelect` | `members={useMembers().members}` — renders each option as a `MemberChip`; `MEMBER_UNASSIGNED` marks its optional "unassigned" option |
-| A comment thread | `EntryList` + `CommentComposer` | `useComments` state; `resolveMember` reads each comment's own `author` (`{ name, image }`) — no roster needed |
+| A comment thread | `Timeline` + `Composer` (`@lotics/ui/composer`) | `useComments` state; `resolveMember` reads each comment's own `author` (`{ name, image }`) — no roster needed |
 
 The SDK never imports `@lotics/ui` — the app owns the (thin) data→UI adapter in each row above.
 

package/package.json

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