@antzsoft/chat-core 1.1.1 → 1.1.2

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.1.0 Release Notes</a></li>
+    <li><a href="#whats-new">v1.1.2 Release Notes</a></li>
   </ul>
 
   <div class="section-label">Getting Started</div>
@@ -242,12 +242,174 @@ 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.1.0 (current) ── -->
-  <div class="wn-version open" id="wn-110">
+  <!-- ── v1.1.2 (current) ── -->
+  <div class="wn-version open" id="wn-112">
+    <div class="wn-header" onclick="toggleVersion('wn-112')">
+      <div class="wn-title">
+        <span class="wn-ver">v1.1.2</span>
+        <span class="wn-badge current">Current</span>
+        <span class="wn-date">May 2026</span>
+      </div>
+      <span class="wn-chevron">▲</span>
+    </div>
+    <div class="wn-body">
+
+      <div class="wn-item" id="wn-112-1">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-1')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title">Participants stored in a dedicated collection</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Participants are no longer embedded inside conversation documents. Each participant is now its own document in a separate <code>chat_conversation_participants</code> collection.</p>
+          <p>This removes the MongoDB 16 MB document size ceiling for large groups, eliminates write contention when many members join or leave simultaneously, and allows per-user data (mute, pin, notification settings) to be updated without touching the conversation document.</p>
+          <p><strong>No client API changes.</strong> All existing SDK calls, types, and socket events are unaffected.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-2">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-2')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title">Transit encryption</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>All socket payloads are now encrypted end-to-end using a per-session symmetric key negotiated on connect via a server-side handshake. Encryption and decryption are handled transparently inside the SDK — no changes to how you call <code>sendMessage</code>, <code>socketEmit</code>, or any event listeners.</p>
+          <p><strong>No action required.</strong> Existing callers work without modification.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-3">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-3')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Disbanded groups now visible in read-only mode for removed members</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When a group was disbanded (all members left or removed), removed participants had an inconsistent view — the conversation sometimes disappeared entirely before they could dismiss it. Removed participants now always see the conversation in read-only mode until they explicitly call <code>leave()</code> to hide it from their list.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-4">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-4')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Removed participant access hardened</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Three access control gaps closed for removed users:</p>
+          <ul>
+            <li><strong>Message history capped at removal time</strong> — The REST message list API now applies a <code>createdAt ≤ removedAt</code> filter for removed participants. Messages sent after removal are no longer visible.</li>
+            <li><strong>Search, starred messages, and unread counts blocked</strong> — Removed users could previously search messages, view their starred messages, and fetch unread counts from conversations they were removed from. All three endpoints now check active membership before returning results.</li>
+            <li><strong>Socket and push already enforced</strong> — Real-time events and push notifications were already blocked at the socket room level (room kick on removal). No change here.</li>
+          </ul>
+          <p><strong>No client action required.</strong> These are server-side enforcement fixes.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-5">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-5')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Unread badge drops to zero immediately when admin removes a user</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When an admin removed a user from a group, the removed user's unread badge stayed non-zero until they manually opened the conversation. The server now bulk-inserts read records for all unread messages in that conversation at the moment of removal, so the badge correctly drops to zero immediately.</p>
+          <p><strong>No client action required.</strong></p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-6">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-6')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Compression metadata now stored on the server</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When a compressed image was uploaded via <code>uploadBatch</code>, the file record on the server silently dropped <code>compressed</code>, <code>originalSize</code>, and <code>compressionAlgorithm</code> due to DTO validation stripping unknown fields. These are now correctly persisted.</p>
+          <p><strong>No client action required.</strong> <code>uploadBatch</code> already sends this metadata — it will now be saved automatically.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-112-7">
+        <div class="wn-item-header" onclick="toggleItem('wn-112-7')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Delete for me also removes the message from your starred list</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Calling <code>deleteForMe</code> on a starred message hid it from the message list but left it in the starred messages list. The server now removes the star record at the same time as the delete-for-me record. The message no longer appears in <code>getStarredMessages</code> after being deleted for the requesting user.</p>
+          <p><strong>No client action required.</strong></p>
+        </div>
+      </div>
+
+    </div>
+  </div><!-- /.wn-version -->
+
+  <!-- ── v1.1.1 ── -->
+  <div class="wn-version" id="wn-111">
+    <div class="wn-header" onclick="toggleVersion('wn-111')">
+      <div class="wn-title">
+        <span class="wn-ver">v1.1.1</span>
+        <span class="wn-date">May 2026</span>
+      </div>
+      <span class="wn-chevron">▲</span>
+    </div>
+    <div class="wn-body">
+
+      <div class="wn-item" id="wn-111-1">
+        <div class="wn-item-header" onclick="toggleItem('wn-111-1')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title">Attachment snapshot on reply messages</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p><code>replyTo</code> now includes an <code>attachmentSnapshot</code> field containing a snapshot of the first attachment from the quoted message: <code>type</code>, <code>filename</code>, <code>mimeType</code>, <code>size</code>, <code>duration</code>, <code>dimensions</code>, and a signed <code>url</code>.</p>
+          <p>The snapshot is stored at write time so reply bubbles can render the quoted attachment preview without fetching the original message. A new <code>ReplyAttachmentSnapshot</code> type is exported from the SDK.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-111-2">
+        <div class="wn-item-header" onclick="toggleItem('wn-111-2')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title"><code>contentPreview</code> for multi-attachment replies</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When replying to a message with multiple attachments, <code>replyTo.contentPreview</code> now reflects the full count: <code>"photo.jpg +2 more"</code>, <code>"3 Photos"</code>, <code>"3 Attachments"</code> (mixed types). Previously it always showed only the first filename regardless of how many attachments the quoted message had.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-111-3">
+        <div class="wn-item-header" onclick="toggleItem('wn-111-3')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Pin, unpin, and unmute operations</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Server-side issues causing pin, unpin, and unmute to fail in certain states are resolved. All three operations now complete reliably. <strong>No client action required.</strong></p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-111-4">
+        <div class="wn-item-header" onclick="toggleItem('wn-111-4')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Various backend fixes</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Stability and correctness improvements across multiple server-side paths. <strong>No client action required.</strong></p>
+        </div>
+      </div>
+
+    </div>
+  </div><!-- /.wn-version -->
+
+  <!-- ── v1.1.0 ── -->
+  <div class="wn-version" id="wn-110">
     <div class="wn-header" onclick="toggleVersion('wn-110')">
       <div class="wn-title">
         <span class="wn-ver">v1.1.0</span>
-        <span class="wn-badge current">Current</span>
         <span class="wn-date">May 2026</span>
       </div>
       <span class="wn-chevron">▲</span>
@@ -430,7 +592,7 @@ section.sec>h2:hover{color:#fff}
           <span class="wn-chevron-sm">▾</span>
         </div>
         <div class="wn-item-body">
-          <p>The <code>participant_left</code> socket event was only broadcast to the <code>conversation:&lt;id&gt;</code> room. Users only join that room when they actively open that specific conversation — so users on the conversation-list screen never received the event and saw a stale participant count. The server now also emits directly to each remaining participant's personal <code>user:&lt;tenantId&gt;:&lt;userId&gt;</code> room, skipping users already in the conversation room to avoid double-delivery.</p>
+          <p>The <code>participant_left</code> socket event was only broadcast to the <code>conversation:&lt;tenantId&gt;:&lt;id&gt;</code> room. Users only join that room when they actively open that specific conversation — so users on the conversation-list screen never received the event and saw a stale participant count. The server now also emits directly to each remaining participant's personal <code>user:&lt;tenantId&gt;:&lt;userId&gt;</code> room, skipping users already in the conversation room to avoid double-delivery.</p>
           <p><strong>Action required:</strong> None. Server-side fix only.</p>
         </div>
       </div>
@@ -1217,7 +1379,7 @@ npx pod-install</code></pre>
       <tr><td><code>userId</code></td><td><code>string</code></td><td>External auth</td><td>Your system's user ID</td></tr>
       <tr><td><code>avatar.url</code></td><td><code>string</code></td><td>No</td><td>Avatar URL — pass <code>url</code> OR <code>base64</code>, not both</td></tr>
       <tr><td><code>avatar.base64</code></td><td><code>string</code></td><td>No</td><td>Raw base64 avatar string</td></tr>
-      <tr><td><code>encryptionMode</code></td><td><code>'none'|'server'</code></td><td>No</td><td>Defaults to <code>'none'</code></td></tr>
+      <tr><td><code>transitEncryption</code></td><td><code>boolean</code></td><td>No</td><td>Payload-level wire encryption: encrypts every HTTP request/response and socket event using ECDH key exchange + AES-256-GCM. Default: <code>true</code>. Server must have <code>TRANSIT_ENCRYPTION_ENABLED=true</code> (default). Safe to toggle anytime — wire-only, nothing stored. Set <code>false</code> for local development only.</td></tr>
       <tr><td><code>upload</code></td><td><code>UploadConfig</code></td><td>No</td><td>File size limits, allowed types, progress callback</td></tr>
     </tbody>
   </table>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antzsoft/chat-core",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "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",