edfcore 0.4.304 → 0.4.306

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

package/docs/CHANGELOG.md

@@ -6,6 +6,31 @@ 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.306
+
+- **Built** the file `discontinuous.md` draws and read it. The page opens with a diagram — six
+  one-second records with a ten-second gap between record 2 and record 3 — and everything after is
+  arithmetic on that picture: which chunk starts where, which carries the gap, that a two-record
+  read either side spans twelve seconds for two seconds of data, and that `locate(13.5)` answers
+  record 3 at 13 s plus half a second.
+- Those figures are the page's argument. "Reading such a file as if it were contiguous puts record
+  3 at t = 3 s when it truly starts at t = 13 s. Nothing throws, the waveform looks fine, and every
+  event you align against it is ten seconds out." `discontinuous.test.ts` covers EDF+D thoroughly
+  against a different fixture — hour-long intervals in a sleep latency test — so this builds the
+  page's own file, and the numbers a reader copies are the ones a run produces.
+
+## 0.4.305
+
+- **Pinned** the budget refusal `large-files.md` prints — `requiredBytes` 442,368,000,
+  `budgetBytes` 268,435,456, `optionName` `'maxMaterializeBytes'`. The middle one is the 256 MiB
+  default; the first is every record of the eight-hour file measured in RECORD bytes, not the
+  Int32Array one channel would decode into. Those two differ by an order of magnitude here and the
+  smaller would have looked just as plausible on the page, which is the sort of number a reader
+  copies into a capacity estimate.
+- `optionName` is checked by triggering a real refusal rather than by reading the type: the field
+  exists so a message can point at an argument the caller can actually change, and a message
+  naming an option that had been renamed would be worse than none.
+
 ## 0.4.304
 
 - **Executed** the costing on `large-files.md`. Its whole argument is numeric: an eight-hour,

package/package.json

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