edfcore 0.4.317 → 0.4.319

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.317";
+export declare const VERSION = "0.4.319";
 //# 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.317';
+export const VERSION = '0.4.319';
 //# 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.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.
+  `physical-values.md` justifies pinning EDFlib's expression with one measurement — the textbook
+  form "fails it on 140 of 256 samples of the symmetric fixture", with an example pair of values —
+  and the existing assertion was that more than a quarter of the asymmetric file's samples differ.
+- That bound is the right shape for "the fixtures are not vacuous" and the wrong shape for a
+  sentence quoting an exact count and an exact pair of decimals. Both numbers and both values are
+  now read out of the page and reproduced from the committed pyEDFlib output, so the page's
+  evidence is measured rather than remembered. The looser bound stays; it says something different.
+
 ## 0.4.317
 
 - **Added** an execution of the out-of-range section of `physical-values.md` — the four samples the

package/package.json

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