edfcore 0.2.48 → 0.2.50

package/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.2.50
+
+- **Added** a corpus-coverage report that always runs. Every other test in `tests/corpus/` skips
+  when the files are absent, which is right — a fresh clone must stay green and offline, and none
+  of the corpus is redistributed. But a skipped test is indistinguishable from a passing one in a
+  summary line, and the corpus is where this project's strongest claims live: `1487 passed` reads
+  the same whether the bit-for-bit check against a 22-hour clinical recording ran or not. It now
+  says which state the run is in, once, in a line a reader sees.
+- It also checks the parts that need no corpus: every manifest entry names a source, a licence and
+  a SHA-256, no committed golden refers to a file the manifest no longer lists, and every fetched
+  file has a parity golden. A golden that has drifted from the corpus definition still looks like
+  coverage, which is the failure this catches.
+
+## 0.2.49
+
+- **Added** annotation, start-date and geometry parity on the real corpus, alongside the sample
+  parity added in 0.2.48. The richest case is the sleep-edfx hypnogram: **154 sleep stages on a
+  file whose record duration is legally zero** — the case where `sampleRateHz` is `undefined` and
+  every rate-derived expression yields `NaN`, so a reader that indexes by rate rather than by
+  record cannot read it at all. edfcore finds the same 154 events at the same onsets with the same
+  durations as pyEDFlib, and the epochs tile the night with no gap, checked against pyEDFlib's
+  onsets rather than against edfcore's.
+- Start dates too. The sleep-edfx files were recorded in 1989 and carry a two-digit year, so
+  resolving them exercises the 1985-2084 pivot rule against a reader that implements it
+  independently.
+- No discrepancy was found. That is the result, and it is worth stating plainly rather than
+  implying the sweep found something.
+
 ## 0.2.48
 
 - **Added** bit-for-bit parity against pyEDFlib on the REAL corpus — the last thing the README

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.2.48";
+export declare const VERSION = "0.2.50";
 //# 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.2.48';
+export const VERSION = '0.2.50';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.2.48",
+  "version": "0.2.50",
   "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.2.48';
+export const VERSION = '0.2.50';