edfcore 0.4.318 → 0.4.320

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

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.4.320
+
+- **Extended** 0.4.319 to the second copy of the harness table. `scripts/golden/README.md` carries
+  the complete one — four rows rather than the documentation page's three, because it includes
+  `corpus-parity.test.ts`, the only harness whose inputs nobody here chose — and `tests/README.md`
+  sends the reader to it for "what each harness claims and how strong that claim is".
+- That copy names each harness by file, which is the stronger form, so a row cannot outlive the
+  test it describes. Every named file has to exist, every bit-for-bit row has to belong to a
+  harness that compares with `Object.is` and no tolerance, and the MNE bound has to match both the
+  constant in the harness and the figure the other table publishes.
+
+## 0.4.319
+
+- **Added** a check that the three cross-implementation harnesses claim on the page exactly what
+  they assert in code. `physical-values.md` tabulates them precisely because they are not equally
+  strong — pyEDFlib values bit for bit, pyEDFlib onsets exact to the tick, MNE only to 1e-12
+  relative and explicitly not bit-exact — and that is a claim about the tests, so no test could
+  previously be wrong about it in a way that showed.
+- The MNE bound is now read out of `mne-parity.test.ts` rather than restated: loosening that one
+  constant for a flaky run would otherwise leave the page publishing a parity claim a thousand
+  times stronger than the one being made, with the whole suite still green. The two exact rows are
+  checked for the ABSENCE of a tolerance, with comments stripped first — `golden-values.test.ts`
+  explains at length why it does not use one, and the explanation must not vouch for itself.
+
 ## 0.4.318
 
 - **Strengthened** the check that the golden fixtures can tell the two scaling forms apart.

package/package.json

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