cross-tab-worker-databus 0.21.20 → 0.21.22

package/dist/{chunk-VQZXIMXR.js → chunk-ISYP7LVP.js}

@@ -1735,10 +1735,11 @@ var DataBusTraceReporter = class {
   }
   /** Synchronous snapshot of the current metrics window without resetting it.
    * Returns the same derived counters as a periodic `message_metrics` event,
-   * or null when metrics recording is inactive (disabled or events-only mode).
-   * The window keeps accumulating until the next interval flush. */
+   * or null when metrics recording is inactive, which covers each of disabled,
+   * stopped and events-only mode. The window keeps accumulating until the next
+   * interval flush. */
   getMetrics() {
-    if (!this.metricsActive || this.stopped) return null;
+    if (!this.metricsActive) return null;
     const timestamp = this.now();
     const samples = this.latencySamples;
     return {
@@ -1814,15 +1815,28 @@ var DataBusTraceReporter = class {
   }
   /** True when metrics recording is active: enabled, not stopped, and the mode
    * includes metrics. Extracted so the seven readers — `getMetrics`, the five
-   * `record*` methods and `flush` — share one guard instead of repeating it.
-   * The `!stopped` term is part of the contract, not a bonus: `event()` does not
-   * go through this getter and gates on `stopped` itself. */
+   * `record*` methods and `flush` — share one guard instead of repeating it, which
+   * leaves `stopped` read in exactly two places: this term, and `event()`, which
+   * skips metrics entirely and so gates on the field itself.
+   *
+   * Do not add a `|| this.stopped` back at a call site. `getMetrics` and `flush`
+   * each carried one, and the repetition is what made this term look untestable:
+   * deleting the term left all 37 test files green, because a read of a field the
+   * guard consulted one expression earlier can never be the decider. With both
+   * repeats gone the same deletion dies twice in `tests/trace.test.ts` — to
+   * "starts a fresh metrics window after pause and resume, and stop prevents later
+   * flushes", and to "getMetrics returns null while metrics recording is inactive",
+   * whose name promises all three inactive cases and which tested two of them until
+   * this file stopped absorbing the third. What the term holds: `stop()` resets the
+   * counters through `pause()` before any later call can reach them, so without it a
+   * `record*` during a stopped window accumulates unreset and `start()` — which
+   * clears `stopped` without resetting — hands it to the new session's window. */
   get metricsActive() {
     return this.enabled && !this.stopped && this.mode !== TRACE_MODE.EVENTS;
   }
   /** Emit the accumulated metrics snapshot if the interval is active. */
   flush() {
-    if (!this.metricsActive || this.stopped) return;
+    if (!this.metricsActive) return;
     this.flushNow();
   }
   flushNow() {
@@ -2463,14 +2477,14 @@ var DedupManager = class {
 var SDK_VERSION = (
   // The `''` arm has zero counts in every coverage run and cannot be lit from a
   // test: `vitest.config.ts` defines the global for the whole suite, and so does
-  // each bundle `scripts/build.mjs` emits, so reaching this side needs a consumer
-  // that bundles `src/` without passing the define — which is also the only
-  // consumer this module is read by at source level. It cannot be deleted either,
-  // since the declaration's type is `string | undefined` and the export's is
-  // `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.20" : ""
+  // each bundle `scripts/build.mjs` emits, so reaching this side needs a tool that
+  // consumes `src/` without passing the define — and this repository has none. The
+  // two source-level readers are named in the header above, and only one of them
+  // evaluates this expression. It cannot be deleted either, since the
+  // declaration's type is `string | undefined` and the export's is `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.22" : ""
 );
 
 // src/core/data-bus.ts
@@ -3406,8 +3420,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({
@@ -3702,4 +3718,4 @@ export {
   parseDataBusPublication,
   selectWorkerBackend
 };
-//# sourceMappingURL=chunk-VQZXIMXR.js.map
+//# sourceMappingURL=chunk-ISYP7LVP.js.map