edfcore 0.4.492 → 0.4.494

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

package/docs/CHANGELOG.md

@@ -6,6 +6,37 @@ 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.494
+
+- **Added** a test that produces the refusal `large-files.md` prints. That page's budget section is
+  a transcript — three field values and the whole error message, wrapped over three lines, for a
+  named file — and nothing had compared any of it with what `readRecords` throws.
+- A message reworded in `io/read.ts` leaves a transcript on the site that no version of edfcore has
+  ever produced, and the transcript is the part a reader searches for when they hit the error.
+  `budget-boundary.test.ts` owns the rule; this owns the page.
+- The file on that page is 442 MB and is never built. `readRecords` refuses before it allocates or
+  reads, which is the property the section is about, so a source reporting the length and serving
+  the header is all this needs — and the last case counts the bytes to prove the refusal really did
+  come first, rather than after a 442,368,000-byte read of zeros.
+- Every number is read out of the page, including the geometry in the sentence that introduces the
+  file, so a fixture drifting from the prose fails rather than agreeing about the wrong recording.
+
+## 0.4.493
+
+- **Added** the two edges of `readHeader`'s prefetch decision, both of which could be moved with
+  the suite green.
+- The upper one is the one that matters. Narrowing `<= 9999` refuses the hint for a file declaring
+  the most signals a header can — and the consequence is not a slower read but a wrong answer: the
+  second read is skipped, `parseHeader` gets a quarter of a kilobyte of a 2.56 MB header, and a
+  perfectly good recording is reported `SOURCE_TOO_SMALL`. At exactly one signal count.
+- The other side of that guard is unreachable, and the test says so with a check rather than in
+  prose: the field is four ASCII bytes and `parseEdfInteger` admits no exponent, so `9999` is the
+  largest value that parses. Widening the field or admitting `9e9` makes the guard live, and fails
+  this in the same commit.
+- The lower edge is a source that ends with the fixed header. `remaining` is zero, and asking for
+  zero bytes is still a read — a round trip over HTTP, and an entry in every read-count claim this
+  file makes.
+
 ## 0.4.492
 
 - **Added** a test that runs the worked example on `reading-signals.md`. That page carries the

package/package.json

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