cross-tab-worker-databus 0.21.19 → 0.21.21

package/dist/cjs/centrifuge.cjs

@@ -2599,7 +2599,7 @@ var SDK_VERSION = (
   // `string` (dropping the conditional is TS2322, measured). Recorded here so the
   // leg reads as a shape the harness cannot reach rather than as a case nobody
   // exercised.
-  true ? "0.21.19" : ""
+  true ? "0.21.21" : ""
 );
 
 // src/core/data-bus.ts
@@ -3535,8 +3535,10 @@ var CrossTabDataBus = class {
    * wrong mechanism and was the shipped claim until it was measured: a snapshot
    * taken with the opening still unresolved already listed the route, its
    * confirmation and both tabs' worker records, because
-   * `BatchingStorageWriter` serves pending writes on read (`storage-batch.ts:79-82`
-   * for `getItem`, `:143-155` for the `keys()` union that `readAllByPrefix` uses). */
+   * `BatchingStorageWriter` serves pending writes on read — `getItem` returns the
+   * pending value before touching the store, and the private `keys()` union of
+   * persisted keys, pending writes minus pending deletes is what `readAllByPrefix`
+   * walks. */
   emitCoordinationTrace() {
     const snapshot = this.cluster.getSnapshot();
     this.trace.event({
@@ -3951,7 +3953,8 @@ var CentrifugeSession = class {
    * Measured — deleting this line leaves all 37 test files green, and the frame
    * it withholds has nowhere to land anyway: the only handler registry is the
    * DataBus's `topicHandlers`, and every write to it sits behind
-   * `assertPublicTopic` (`data-bus.ts:929`, `:1009`, `:1033`), so no `''` key can
+   * `assertPublicTopic` (at the head of `data-bus.ts`'s `subscribe()`, `publish()`
+   * and `publishBatch()`), so no `''` key can
    * exist — while `topicMatchesPattern` answers false for an empty topic against
    * both `*` and `prefix.*`, so a wildcard handler cannot see it either. Neither
    * of those is a reason to delete this guard: it is the only one *at this layer*,