edfcore 0.4.366 → 0.4.368

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.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
+  to the adapter table under them. The shims exist so neither the DOM nor `@types/node` leaks into
+  the published `.d.ts` — naming `Blob` forces `lib.dom` on every consumer — and each is the
+  minimum shape edfcore uses.
+- `shim-assignability.test-d.ts` already proves a `Blob`, a `File`, an `AbortSignal` and a
+  `Response` all fit. What it cannot see is whether the page prints the same shape it proves things
+  about, and a shim is exactly the declaration someone copies off a page to build a test double
+  from: a member the page shows and the type does not is a double that compiles against the page
+  and is refused by the library.
+- `FetchLike` is checked for an absence instead. `signal` is deliberately not in its printed `init`
+  and is still passed at runtime, because naming it would break the assignability of
+  `globalThis.fetch` — so the check is that it stays absent from both, and that the page still
+  explains why, since without the explanation the omission reads as an oversight.
+- The adapter table's rows now have to name real exports from the entry point each row names, with
+  the two filesystem adapters behind `edfcore/node` and everything else reachable from the
+  universal entry — the split the shims exist to protect.
+
 ## 0.4.366
 
 - **Added** a check that every version number this repository cites is one it released. The

package/package.json

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