edfcore 0.5.17 → 0.5.19

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

package/docs/CHANGELOG.md

@@ -6,6 +6,50 @@ 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.5.19
+
+- **Added** the table on `diagnostics.md` that says which calls take `strict`. Eleven functions in
+  two columns, and nothing read it. `strict-decision.test.ts` covers what `strict` does — the info
+  exemption, the four always-fatal conditions — and `strict-reaches.test.ts` how far into a file it
+  reaches. Which entry points accept it at all was prose.
+- It is the kind of table that goes stale silently, in both directions. A function that grows a
+  `ParseOptions` parameter joins the left column without anyone editing the page, and a caller
+  reading the right column concludes it cannot be made strict. A function whose options type is
+  narrowed leaves the left column the same way, and a caller passing `strict` to it gets one that is
+  quietly ignored — an option that type-checks, runs, and does nothing.
+- The two columns are checked by different means, because they are different claims. The six on the
+  left are **driven**: each is given a file with a real non-`info` defect — a non-standard reserved
+  field for the header three, a malformed TAL for the annotation three — and each must throw
+  `EdfFormatError` carrying that code under `strict: true` and collect the same diagnostic without
+  it. That is the only way to catch a `strict` that is accepted and dropped.
+- The five on the right are checked **structurally**, out of `src/`: each function's options
+  parameter is resolved to its declared type, the `extends` and `&` chain is followed, and `strict`
+  must not be reachable through it. A behavioural check cannot prove that negative — passing an
+  option a signature does not declare is a compile error, not a runtime one. The same resolver is
+  then pointed at the left column, which is what keeps the two halves honest.
+
+## 0.5.18
+
+- **Added** the unscalable signal `diagnostics.md` walks through, run from the throw to the read.
+  That page uses one file for three separate arguments and prints values for all three — the
+  `strict` transcript, the callout headed "`errors > 0` does not mean the file failed to read", and
+  the `EdfScalingError` block at the bottom. They are the same signal seen from three angles, and
+  none of the three was run.
+- The `strict` transcript is four fields off a thrown error and a fifth off the diagnostic inside
+  it: `DEGENERATE_DIGITAL_RANGE digitalMinimum 504 1`, then `EDF+ additional specification 5`. The
+  `504` is the sharpest of them — the byte at which signal 1's `digitalMinimum` field starts in a
+  two-signal file, `256 + 2 x 120 + 8`, and the number a reader would take to a hex editor. It is
+  now asserted against that arithmetic as well as against the page. `error-fields.test.ts` checks
+  the fields exist and `spec-references.test.ts` that every diagnostic cites something; neither was
+  pointed at this file.
+- "The error carries the whole `diagnostic` it would otherwise have recorded, so nothing is lost by
+  throwing" is checked by comparing what the strict throw carries against what the non-strict parse
+  of the same bytes collected.
+- The callout is the part worth having pinned. It says `errors > 0` **and** `report.ok === false`
+  are both true of a file that reads perfectly, and tells the reader to gate on the thrown
+  `EdfError` instead — three values agreeing on one file, asserted in prose. All three are now read
+  off that file, alongside the other signal converting to eight finite microvolt values.
+
 ## 0.5.17
 
 - **Added** the record onsets that quietly stop being true when a read is narrowed to a secondary

package/package.json

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