edfcore 0.2.54 → 0.2.56

package/CHANGELOG.md

@@ -6,6 +6,32 @@ 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.56
+
+- **Fixed** `tests/README.md`, which said "There are no binary fixtures in this repository" and
+  listed Tier 2 of its own fixture policy as "Not used". Both stopped being true in 0.2.34, when
+  the parity harness committed six small EDF/BDF files and their goldens — about 1.4 MB. I added
+  those without revisiting the policy that forbade them.
+- The policy is now stated as it actually is, with the reason: a parity fixture has to be bytes a
+  DIFFERENT implementation wrote, so regenerating it in memory with this project's own writer
+  would make the comparison circular and prove nothing. The licence rule is unchanged and was
+  never at risk — the committed files are generated locally by pyEDFlib, the downloaded corpus is
+  still gitignored, and only the JSON goldens reference it, by name and hash. None of it ships:
+  the package contains `dist`, `src` and the changelog.
+
+## 0.2.55
+
+- **Added** CLI coverage against the real corpus. Every existing CLI fixture is a few hundred bytes
+  written by this project, which checks the decisions — exit codes, flags, output shape — and
+  cannot check what a command does when pointed at 48 MB of clinical recording, or at a scoring
+  file with 154 events and a record duration of zero.
+- The load-bearing one: **`edfcore validate` exits 0 on a real recording from a real sleep lab.**
+  That is what makes the command usable as a CI gate at all; a validator that fails real files is
+  worse than no validator, because it teaches people to ignore it.
+- Also pins that the sleep-edfx PSG is plain **EDF, not EDF+** — it carries an `Event marker` data
+  channel rather than an annotations channel, which is how that dataset splits signals from
+  scoring. I had assumed EDF+ writing the test and the file said otherwise.
+
 ## 0.2.54
 
 - **Added** the random-access claim, measured over HTTP on the real 48 MB recording. A `fetch`

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

package/package.json

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