edfcore 0.4.367 → 0.4.369

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

package/docs/CHANGELOG.md

@@ -6,6 +6,39 @@ 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.369
+
+- **Added** a check over what a `ValidationReport` promises on `validation.md`. `ok` is the field a
+  caller branches on and means less than it looks like — exactly "no diagnostic has severity
+  `error`", not a claim that the file is conformant, and a false `ok` not a claim it is unreadable.
+  The four codes the page says survive to a report at that severity are checked to be the only ones
+  that do, on a file where one signal has no scale and the other is fine.
+- The sentence pinned hardest is the one about what cannot appear: no always-fatal code reaches a
+  report, because a file carrying one cannot be opened, and a report about such a file would be
+  incoherent rather than merely wrong. The single exception is asserted from the other side —
+  `TIMELINE_NOT_MONOTONIC` makes the sweep reject.
+- `signalStats` has a shape a caller indexes by: one entry per data signal in `dataSignalIndices`
+  order, with annotation channels excluded because their bytes are text, so an off-by-one gives
+  every channel its neighbour's statistics. And a signal with no samples reports zeroes rather than
+  infinities — `-Infinity` is what an unseeded reduce produces, and it is a number a caller would
+  plot.
+
+## 0.4.368
+
+- **Added** `tests/property/inspect-safety.test.ts`. `inspectEdf` is the triage call and makes the
+  strongest promise in the package: `openEdf` and `parseHeader` promise to throw an `EdfError`
+  rather than escape the error model, and `fuzz.test.ts` holds them to that over flipped, random
+  and truncated bytes — `inspectEdf` promises not to throw about content at all. That promise had
+  only ever been tested against fixtures somebody wrote.
+- A promise of the form "never, for any input" is exactly the kind a fixture cannot establish: the
+  inputs a person thinks of are the ones already handled, and the four defects fuzzing found during
+  development were all of that shape. Random bytes, random bytes behind a valid version block, a
+  bit flipped anywhere, and every truncation length exhaustively now go through it.
+- The report is checked as well as the call, because "never returns believable garbage" is the
+  fourth clause of the safety invariant and a triage report full of `NaN` would satisfy "did not
+  throw" while telling a reader nothing true. Every source is in memory, so nothing can fail except
+  on what the bytes say — which makes any rejection a broken promise rather than an ambiguous one.
+
 ## 0.4.367
 
 - **Extended** 0.4.338's interface check to the three structural shims `api-sources.md` prints and

package/package.json

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