@abloatai/humans 0.66.2 → 0.66.4

package/dist/local/sync/SubscriptionManager.d.ts

@@ -137,12 +137,12 @@ export declare class SubscriptionManager {
     /**
      * Re-asserts the full desired set against the transport, forgetting what was
      * previously confirmed. Call this after a reconnect: a fresh
-     * {@link SyncWebSocket} starts from the sync groups named in the connect-time
-     * URL, so the manager's diff baseline no longer reflects the new socket.
+     * {@link SyncWebSocket} starts from the groups confirmed during connection,
+     * so the manager's diff baseline no longer reflects the new socket.
      * Clearing that baseline makes the next reconcile push one
      * `update_subscription` frame that re-establishes the current interest —
      * including any warm or pinned groups that drifted while the connection was
-     * down. The connect-time URL already carries the last-acknowledged set, so
+     * down. The connection already carries the last-acknowledged set, so
      * this is a correction, not the primary mechanism.
      */
     resync(): Promise<void>;

package/dist/local/sync/SubscriptionManager.js

@@ -174,12 +174,12 @@ export class SubscriptionManager {
     /**
      * Re-asserts the full desired set against the transport, forgetting what was
      * previously confirmed. Call this after a reconnect: a fresh
-     * {@link SyncWebSocket} starts from the sync groups named in the connect-time
-     * URL, so the manager's diff baseline no longer reflects the new socket.
+     * {@link SyncWebSocket} starts from the groups confirmed during connection,
+     * so the manager's diff baseline no longer reflects the new socket.
      * Clearing that baseline makes the next reconcile push one
      * `update_subscription` frame that re-establishes the current interest —
      * including any warm or pinned groups that drifted while the connection was
-     * down. The connect-time URL already carries the last-acknowledged set, so
+     * down. The connection already carries the last-acknowledged set, so
      * this is a correction, not the primary mechanism.
      */
     resync() {

package/dist/local/sync/socketEventWiring.js

@@ -11,9 +11,9 @@ export function wireSocketEvents(deps) {
             deps.updateSyncStatus({ offlineSince: undefined });
         }
         // Re-assert read interest on every (re)connect. After a transient
-        // reconnect the socket re-sends its URL groups, but interest may have
-        // changed while offline; after a full reconnect the new socket's URL
-        // carries only base groups. `resync` re-pushes the current desired set
+        // reconnect the socket restores its last confirmed groups, but interest
+        // may have changed while offline; after a full reconnect the new socket
+        // starts with only base groups. `resync` re-pushes the current desired set
         // so the server-side index matches what the user is actually viewing.
         void deps.areaOfInterest.resync();
     });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abloatai/humans",
-  "version": "0.66.2",
+  "version": "0.66.4",
   "description": "The optional human-facing local-state package for Ablo: presence, live queries, and React bindings.",
   "license": "Apache-2.0",
   "type": "module",
@@ -85,7 +85,7 @@
     "directory": "packages/humans"
   },
   "dependencies": {
-    "@abloatai/transaction": "0.66.2",
+    "@abloatai/transaction": "0.66.4",
     "events": "^3.3.0",
     "mobx": "^6.13.7",
     "uuid": "^11.1.0",

package/src/local/sync/SubscriptionManager.ts

@@ -232,12 +232,12 @@ export class SubscriptionManager {
   /**
    * Re-asserts the full desired set against the transport, forgetting what was
    * previously confirmed. Call this after a reconnect: a fresh
-   * {@link SyncWebSocket} starts from the sync groups named in the connect-time
-   * URL, so the manager's diff baseline no longer reflects the new socket.
+   * {@link SyncWebSocket} starts from the groups confirmed during connection,
+   * so the manager's diff baseline no longer reflects the new socket.
    * Clearing that baseline makes the next reconcile push one
    * `update_subscription` frame that re-establishes the current interest —
    * including any warm or pinned groups that drifted while the connection was
-   * down. The connect-time URL already carries the last-acknowledged set, so
+   * down. The connection already carries the last-acknowledged set, so
    * this is a correction, not the primary mechanism.
    */
   resync(): Promise<void> {

package/src/local/sync/socketEventWiring.ts

@@ -49,9 +49,9 @@ export function wireSocketEvents<TCollaboration extends EventMap<TCollaboration>
         deps.updateSyncStatus({ offlineSince: undefined });
       }
       // Re-assert read interest on every (re)connect. After a transient
-      // reconnect the socket re-sends its URL groups, but interest may have
-      // changed while offline; after a full reconnect the new socket's URL
-      // carries only base groups. `resync` re-pushes the current desired set
+      // reconnect the socket restores its last confirmed groups, but interest
+      // may have changed while offline; after a full reconnect the new socket
+      // starts with only base groups. `resync` re-pushes the current desired set
       // so the server-side index matches what the user is actually viewing.
       void deps.areaOfInterest.resync();
     });