edfcore 0.3.100 → 0.3.102

package/CHANGELOG.md

@@ -6,6 +6,42 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.3.102
+
+- **Fixed** `tests/corpus/coverage.test.ts` asserting nothing on the run it exists to protect.
+  - The file's docblock says it "checks the parts that need no corpus at all — that the manifest and
+    the goldens agree. A golden for a file the manifest no longer lists ... is a real drift that no
+    amount of skipping should hide." Its one test early-returned when the corpus was absent, with
+    `expect(corpusGoldens().length).toBeGreaterThanOrEqual(0)`. A length is never negative, so on
+    `git clone && npm test` — no corpus, which is the case the whole file is about — it checked
+    nothing.
+  - The manifest-versus-goldens half is now its own test and always runs: both sides are committed,
+    so it needs no corpus. The half that genuinely needs the files still skips without them, and
+    says so.
+- Canaried in the state that matters: with `tests/corpus/files/` moved away and a manifest entry
+  removed, the new test fails and names the orphaned golden. Before this it passed.
+- Fifth release in this batch about defect shape (e) — a guard that would still pass if what it
+  names regressed. Found by sweeping the whole suite for self-comparisons and structurally weak
+  assertions after 0.3.101, rather than one at a time.
+
+## 0.3.101
+
+- **Fixed** an assertion in `tests/corpus/whole-api.test.ts` that compared a value with itself:
+  `expect(inspection.header.signals.length).toBe(inspection.header.signals.length)`. Both operands
+  are the same expression, so it held for every input.
+  - It was the only consistency check in the test the file's docblock calls "the strongest promise
+    in the package", under a comment reading "Whatever it reports must be internally consistent
+    rather than merely present". Across five corpus files it checked nothing.
+  - Replaced with invariants that can fail: the two index arrays partition the signals exactly once,
+    `headerByteLength` is the `256 * (ns + 1)` the signal count implies, `bytesRead` exceeds neither
+    the file nor the 128 KiB ceiling, and `ok` equals "no error-severity diagnostic" — the rule the
+    `inspectEdf` docblock states.
+- Each new assertion was canaried by breaking the behaviour it names and confirming it fails.
+  Two earlier attempts were rejected: one could not distinguish anything on a clean corpus, and one
+  broke module loading instead of changing behaviour, which is not a canary.
+- Defect shape (e), the one this project keeps re-learning: a guard that would still pass if what it
+  names regressed. It has now been the subject of 0.3.52, 0.3.78, 0.3.80, 0.3.90 and this release.
+
 ## 0.3.100
 
 - **Fixed** `diagnostics.md` recommending, as the alternative to a gate it warns against, a gate

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.3.100";
+export declare const VERSION = "0.3.102";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.100';
+export const VERSION = '0.3.102';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.3.100",
+  "version": "0.3.102",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.100';
+export const VERSION = '0.3.102';