edfcore 0.4.352 → 0.4.354

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.354
+
+- **Added** a compile check over every signature the reference pages print. Four pages open each
+  function with a `ts` fence holding its declaration and nothing else — thirty-odd across
+  `api-primitives`, `api-reading`, `api-sources` and `api-validate` — and every one is hand-typed.
+  They are the first thing a reader sees for a function and what they write their call against.
+- `doc-snippets-compile.test.ts` compiles the fences that are complete programs and skips these: a
+  bare declaration imports nothing, so it never matched the filter that finds runnable examples.
+  The most load-bearing line on each reference page was the one nothing compiled.
+- Assignability is checked in BOTH directions, which is the difference between "the documented
+  shape is usable" and "the documented shape is the real one" — one direction alone accepts a page
+  that widens a parameter or narrows a return, and a widened parameter describes a function that
+  does not exist. Signatures are extracted per fence rather than by scanning the page, because a
+  lazy match for the parameter list's closing paren runs past it into the prose: `Promise<{ … }>`
+  has no `):` to stop at and the next parenthetical sentence does.
+- The types a declaration mentions are resolved through `barrel-types.ts` rather than a hard-coded
+  list. The first version used a list and missed four, which is the failure that helper was
+  extracted to stop repeating.
+
+## 0.4.353
+
+- **Added** a cross-check between the two places `openEdf`'s cost is published. `large-files.md`
+  states it as a four-row table and `api-reading.md` states it as a sentence, and both are read by
+  someone deciding whether opening a file is cheap enough to do on a click.
+- The table was already checked against the library in 0.4.340. This checks the prose against the
+  table, so all three agree rather than two agreeing while a third drifts — the shape this
+  repository keeps finding wrong, in the section list, the diagnostic tables and the `ByteSource`
+  interface before it. It is also the cheaper direction to automate: the prose spells its counts as
+  words, and nobody diffs a word against a digit by eye.
+
 ## 0.4.352
 
 - **Added** `tests/property/window-cost.test.ts`, which states in general what four checks in this

package/package.json

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