edfcore 0.4.463 → 0.4.465

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

package/docs/CHANGELOG.md

@@ -6,6 +6,38 @@ 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.465
+
+- **Added** the close half of `cachedSource`'s pass-through, which had never run. At `maxBytes: 0`
+  the function returns a different object entirely — built and returned before any cache state
+  exists — with its own `read` and its own `close`. The read half was covered twice over; the
+  close half is the one whose failure a test cannot see indirectly.
+- `cachedSource(await fileSource(path), { maxBytes: 0 })` is a reasonable thing to write. The page
+  documents the budget as floored at 0, and wrapping unconditionally while tuning the number per
+  environment is how a caller arrives there. A pass-through that dropped the delegation would hold
+  the descriptor open for the life of the process, with nothing about the reads looking wrong.
+- The optional-`close` case is pinned alongside it: `ByteSource.close` is optional and
+  `byteSource(bytes)` is the adapter that omits it, so `source.close?.()` is what makes closing a
+  zero-budget wrapper over an in-memory file resolve rather than throw a `TypeError` — the shape a
+  caller hits while swapping adapters.
+
+## 0.4.464
+
+- **Added** tests for the `maxMaterializeBytes` boundary in all three modules that check it —
+  `io/read.ts` before a record range, `decode/digital.ts` before the `Int32Array`, and
+  `envelope.ts` before the bucket accumulators. All three admit a requirement equal to the budget,
+  and every existing test set a budget far below what it asked for or far above it, so relaxing
+  any of the three to a strict comparison left the suite green.
+- Equality is the case the option is used in. The documented way to stay inside a budget is to
+  size the request to it — take `maxMaterializeBytes`, divide by `header.recordByteLength`, read
+  that many records — and done exactly that lands ON the number every time. A strict comparison
+  refuses the arithmetic the error message itself recommends, so "read fewer records per call"
+  would be advice a caller had already followed perfectly.
+- Both sides of each boundary, and the refusal is checked to carry the same two numbers on
+  `requiredBytes` and `budgetBytes`. Those are the fields `api-errors.md` documents so a caller can
+  compute the next request instead of guessing at it, and a boundary error that reported them
+  inconsistently would be worse than one that did not report them at all.
+
 ## 0.4.463
 
 - **Added** the half-open edge cases for the branch `trimToWindow` takes when nothing in the chunk

package/package.json

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