@antzsoft/chat-core 1.2.7 → 1.2.9

package/dist/{storage-CW70b4vi.d.cts → storage-BgQYwWPH.d.cts}

@@ -150,6 +150,7 @@ interface Message {
     pinnedBy?: string;
     pinnedAt?: string;
     uploadProgress?: number;
+    seq?: number;
     sentAt: string;
     createdAt: string;
     sender?: User;
@@ -389,6 +390,8 @@ interface MessageAckEvent {
     tempId: string;
     messageId: string;
     status: MessageStatus;
+    /** Present when server supports seq — monotonic counter for this conversation. */
+    seq?: number;
 }
 interface MessageDeliveredEvent {
     messageId: string;
@@ -458,6 +461,10 @@ interface CrossConversationSyncResponse {
 }
 interface ConversationSyncResponse {
     syncedAt: string;
+    /** Present when server supports seq-based sync. Use as afterSeq in next call. */
+    nextSeq?: number;
+    /** True when more pages are available — call again with updated afterSeq. */
+    hasMore?: boolean;
     messages: Message[];
     deletedForMe: SyncDeletedForMe[];
     reactions: SyncReactions;

package/dist/{storage-CW70b4vi.d.ts → storage-BgQYwWPH.d.ts}

@@ -150,6 +150,7 @@ interface Message {
     pinnedBy?: string;
     pinnedAt?: string;
     uploadProgress?: number;
+    seq?: number;
     sentAt: string;
     createdAt: string;
     sender?: User;
@@ -389,6 +390,8 @@ interface MessageAckEvent {
     tempId: string;
     messageId: string;
     status: MessageStatus;
+    /** Present when server supports seq — monotonic counter for this conversation. */
+    seq?: number;
 }
 interface MessageDeliveredEvent {
     messageId: string;
@@ -458,6 +461,10 @@ interface CrossConversationSyncResponse {
 }
 interface ConversationSyncResponse {
     syncedAt: string;
+    /** Present when server supports seq-based sync. Use as afterSeq in next call. */
+    nextSeq?: number;
+    /** True when more pages are available — call again with updated afterSeq. */
+    hasMore?: boolean;
     messages: Message[];
     deletedForMe: SyncDeletedForMe[];
     reactions: SyncReactions;

package/docs/integration-guide.html

@@ -155,7 +155,7 @@ section.sec>h2:hover{color:#fff}
 
   <div class="section-label">What's New</div>
   <ul>
-    <li><a href="#whats-new">v1.2.7 Release Notes</a></li>
+    <li><a href="#whats-new">v1.2.8 Release Notes</a></li>
   </ul>
 
   <div class="section-label">Getting Started</div>
@@ -250,12 +250,75 @@ section.sec>h2:hover{color:#fff}
   <h2>What's New</h2>
   <p style="color:var(--muted);font-size:13px;margin-bottom:20px">Version history and release notes. Click a version to expand.</p>
 
-  <!-- ── v1.2.7 (current) ── -->
+  <!-- ── v1.2.8 (current) ── -->
+  <div class="wn-version open" id="wn-128">
+    <div class="wn-header" onclick="toggleVersion('wn-128')">
+      <div class="wn-title">
+        <span class="wn-ver">v1.2.8</span>
+        <span class="wn-badge current">Current</span>
+        <span class="wn-date">June 2026</span>
+      </div>
+      <span class="wn-chevron">▲</span>
+    </div>
+    <div class="wn-body">
+
+      <div class="wn-item" id="wn-128-delivery-status">
+        <div class="wn-item-header" onclick="toggleItem('wn-128-delivery-status')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title"><code>deliveryStatus</code> on <code>Conversation.lastMessage</code> — tick state in conversation list</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>The conversation list API (<code>GET /conversations</code>) and the <code>conversation_updated</code> socket event now include <code>deliveryStatus</code> on the <code>lastMessage</code> object. This is the tick state of the last message as seen by the sender — stored directly on the conversation document and kept current by the server on every read and delivery event.</p>
+
+          <table>
+            <thead><tr><th>Value</th><th>Meaning</th></tr></thead>
+            <tbody>
+              <tr><td><code>'sent'</code></td><td>Message written to the server — not yet delivered to all recipients</td></tr>
+              <tr><td><code>'delivered'</code></td><td>All active recipients have received the message on at least one device</td></tr>
+              <tr><td><code>'read'</code></td><td>All active recipients have opened and read the message</td></tr>
+            </tbody>
+          </table>
+
+          <p><strong>Usage — rendering tick marks in a conversation list (custom UI):</strong></p>
+          <pre><code><span class="kw">const</span> { data: conversations } = <span class="kw">await</span> conversationsApi.<span class="fn">list</span>();
+
+<span class="kw">for</span> (<span class="kw">const</span> conv <span class="kw">of</span> conversations) {
+  <span class="kw">const</span> lm = conv.lastMessage;
+  <span class="kw">if</span> (!lm) <span class="kw">continue</span>;
+
+  <span class="cm">// Only show ticks on messages sent by the current user</span>
+  <span class="kw">const</span> isMyMessage = lm.senderId === currentUserId;
+  <span class="kw">if</span> (!isMyMessage) <span class="kw">continue</span>;
+
+  <span class="cm">// deliveryStatus: 'sent' | 'delivered' | 'read'</span>
+  <span class="fn">renderTick</span>(conv.id, lm.deliveryStatus ?? <span class="str">'sent'</span>);
+}</code></pre>
+
+          <p><strong>Live updates</strong> — the existing <code>read_receipt</code> socket event continues to carry real-time tick updates while a conversation room is open. <code>deliveryStatus</code> on <code>lastMessage</code> is the cold-start / list-load source of truth; socket events keep it live after that.</p>
+
+          <p><strong>Server-side changes:</strong></p>
+          <ul>
+            <li><code>lastMessage.deliveryStatus</code> is set to <code>'sent'</code> when a new message is written</li>
+            <li>Promoted to <code>'delivered'</code> when all active recipients have a delivery record for that message</li>
+            <li>Promoted to <code>'read'</code> when <code>fullyReadMessageIds</code> includes the last message (i.e. all active recipients have read it)</li>
+            <li>Status never demotes — a conditional update ensures it only advances: <code>sent → delivered → read</code></li>
+          </ul>
+
+          <p><strong>Migration</strong> — existing conversations are backfilled automatically by <code>005_backfill_last_message_delivery_status</code> on first deploy. It queries <code>chat_message_reads</code> and <code>chat_message_deliveries</code> to compute the correct status for each conversation's current last message. No manual step required.</p>
+
+          <p><strong>Backward compatibility</strong> — <code>deliveryStatus</code> defaults to <code>'sent'</code> when absent (<code>lm.deliveryStatus ?? 'sent'</code>). The field was already defined as optional on the <code>Message</code> type — it is now also populated on the <code>lastMessage</code> snapshot. No breaking changes.</p>
+        </div>
+      </div>
+
+    </div>
+  </div><!-- /.wn-version -->
+
+  <!-- ── v1.2.7 ── -->
   <div class="wn-version open" id="wn-127">
     <div class="wn-header" onclick="toggleVersion('wn-127')">
       <div class="wn-title">
         <span class="wn-ver">v1.2.7</span>
-        <span class="wn-badge current">Current</span>
         <span class="wn-date">June 2026</span>
       </div>
       <span class="wn-chevron">▲</span>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antzsoft/chat-core",
-  "version": "1.2.7",
+  "version": "1.2.9",
   "description": "Platform-agnostic core for Antz Chat — API, socket, stores, types. Works in browser, React Native (Expo or bare), and Node.js.",
   "author": "Antz",
   "license": "MIT",