edfcore 0.4.350 → 0.4.351

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

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ 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.351
+
+- **Added** checks for two read counts on `api-reading.md`, a page that opens by inviting them:
+  "They are exact and testable: wrap your source in a recorder and count."
+- Both are about paths a well-formed file never takes, which is why neither had a test.
+  `readHeader` is exactly two reads, and one when the signal-count field is unreadable — because
+  the second read's size is computed from that field, and a speculative read of an unknown size is
+  the thing being avoided. The saved read is not the point: the caller gets `SIGNAL_COUNT_INVALID`
+  rather than a complaint about a byte range, and that is what is asserted.
+- The same distinction on the next line. A file too short for the header it declares is a file
+  defect, `SOURCE_TOO_SMALL`, not an `EdfSourceError` about a range past the end — getting it
+  backwards is not a crash but a truncated recording reported as an I/O error, which sends the
+  reader to their network stack instead of to their file. Also pinned: the probe costs nothing
+  without an annotations signal, and both probed onsets are memoised into the index while a record
+  between them is not.
+
 ## 0.4.350
 
 - **Added** an execution of the truth table on `validation.md` — four rows over two independent

package/package.json

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