@hviana/sema 0.8.0 → 0.8.1

package/test/93-regime-prediction.test.mjs

@@ -1,17 +1,17 @@
 // 93-regime-prediction.test.mjs — the retrieval/composition regime (R8) is
 // exposed as a structured trace step, without changing inference.
 //
-// After the FIRST mechanism runs (cover, which §2.6 places first and floors at
-// 0), the market's whole outcome is already determined by the one cost ladder:
-// the consensus climb runs exactly when `worthRunning(2 * STEP)` is true —
-// CAST (floor 2·STEP) is the cheapest mechanism that first-touches it.  An
-// incumbent at or below that floor prunes CAST and, with it, the climb
+// After the FIRST mechanism runs (cover, which mechanism-market.md places first
+// and floors at 0), the market's whole outcome is already determined by the one
+// cost ladder: the consensus climb runs exactly when `worthRunning(2 * STEP)`
+// is true — CAST (floor 2·STEP) is the cheapest mechanism that first-touches
+// it. An incumbent at or below that floor prunes CAST and, with it, the climb
 // (retrieval); anything above — or no incumbent — runs the full market and the
-// climb (composition).  The step is purely observational: it is built only
-// under a trace (optional-chaining short-circuits it otherwise), and it never
-// alters which candidate wins.  The assertions here check the payload's
-// STRUCTURE and its consistency with the actual market outcome, never that
-// inference itself changed.
+// climb (composition). The step is purely observational: it is built only under
+// a trace (optional-chaining short-circuits it otherwise), and it never alters
+// which candidate wins. The assertions here check the payload's STRUCTURE and
+// its consistency with the actual market outcome, never that inference itself
+// changed.
 
 import { test } from "node:test";
 import assert from "node:assert/strict";

package/test/94-cross-region-budget.test.mjs

@@ -1,7 +1,7 @@
 // 94-cross-region-budget.test.mjs — the cross-region junction ladder shares ONE
 // k·W allowance per evidence tier once atoms are hubs, instead of letting each
-// candidate pair spend its own √N·W drift budget (attention.ts crossRegionVotes,
-// §2.17's derived gate = traverse.atomIsHub).
+// candidate pair spend its own √N·W drift budget (attention.ts
+// crossRegionVotes, saturation.md's derived gate = traverse.atomIsHub).
 //
 // This is a PERFORMANCE regression test, not a behaviour test: the shared
 // budget is byte-identical at every scale — a pair whose container is not

package/test/95-wide-resonance-removed.test.mjs

@@ -4,13 +4,14 @@
 // pipeline-mechanism.ts's REMOVED note).
 //
 // This is a PERFORMANCE regression test, not a behaviour test: the wide list
-// was a PROPOSAL source whose consumers byte-verify every candidate (§2.3), so
-// removing it is byte-identical wherever the bounded sources supply the same
-// candidate set — and the meter's phase map is the only observable that says
-// whether the exhaustive machinery still exists.  Red-on-revert: re-adding
-// wideResonance re-creates the `wideResonance` phase (and, when the query's
-// top hit clears conceptThreshold, a full-index ANN scan inside it), so the
-// phase-absence assertion below fails.
+// was
+// a PROPOSAL source whose consumers byte-verify every candidate
+// (exact-vs-approximate.md), so removing it is byte-identical wherever the
+// bounded sources supply the same candidate set — and the meter's phase map is
+// the only observable that says whether the exhaustive machinery still exists.
+// Red-on-revert: re-adding wideResonance re-creates the `wideResonance` phase
+// (and, when the query's top hit clears conceptThreshold, a full-index ANN scan
+// inside it), so the phase-absence assertion below fails.
 
 import { test } from "node:test";
 import assert from "node:assert/strict";

package/test/96-bytes-walk-termination.test.mjs

@@ -92,12 +92,12 @@ test("bytes() terminates when its memo cannot hold the working set", async () =>
 });
 
 test("differsByOneWindow's reads are capped — no ALL-sentinel read on deposit", async () => {
-  // §2.8: the near-dedup byte check used to open with
+  // bounded-reads.md: the near-dedup byte check used to open with
   // `bytesPrefix(k, Number.MAX_SAFE_INTEGER)` — the ALL sentinel, which routes
-  // to the full materialising `bytes()` — and only THEN compare lengths.  A
+  // to the full materialising `bytes()` — and only THEN compare lengths. A
   // candidate the length test was about to reject had already been rebuilt byte
   // for byte, and that read is what dragged the deposit path into the walk
-  // above.  Lengths now decide first, from the `contentLen` memo.
+  // above. Lengths now decide first, from the `contentLen` memo.
   const src = await import("node:fs").then((fs) =>
     fs.readFileSync(new URL("../src/store.ts", import.meta.url), "utf8")
   );