edfcore 0.4.338 → 0.4.340

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

package/docs/CHANGELOG.md

@@ -6,6 +6,32 @@ 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.340
+
+- **Added** a check for the table `large-files.md` opens with: a read count and a byte count for
+  each of four shapes of file, supporting the sentence that is the reason to reach for this
+  library at all — "That is the entire cost, whatever the file size." All four rows are now opened
+  through a recording source and counted.
+- A read count is not something a type or a lint can hold. It is a property of the call graph and
+  it changes by accident: a helper that fetches a field it already has, a probe that stops
+  short-circuiting on a one-record file, a header read split per signal block. The page names that
+  last one outright, and over HTTP it is the difference between one round trip and sixty-four on a
+  call the caller believes is free — so it is checked on a 64-signal file. Also pinned: the header
+  read uses the computed `256 * (ns + 1)` rather than the byte-length field, checked against a file
+  that declares a wrong one.
+
+## 0.4.339
+
+- **Added** the three refusals `quick-start.md` promises, each of which is a single clause on the
+  page and a real guard in the library: passing the annotations index to `readWindow` throws rather
+  than plotting timestamped text as a waveform, a label differing only in case is refused because
+  matching is exact and case-sensitive, and a duplicated label is refused rather than resolved to
+  the first.
+- The detail the page attaches to each is checked too, not just that something throws. The
+  not-found error has to list every label in the file — all three, not only the near miss — and the
+  ambiguous one has to name the indices that carry the label, which is what makes either message
+  actionable rather than a report that the call did not work.
+
 ## 0.4.338
 
 - **Added** a check that the three published copies of `ByteSource` agree. It is the one type a

package/package.json

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