edfcore 0.4.272 → 0.4.274

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.274
+
+- **Added** the check that edfcore never writes to the console. The README says it twice, and the
+  survey table explaining why this library exists lists what the alternatives do instead —
+  "`console.warn` and `null`, or bare thrown strings". Diagnostics are values on the result
+  precisely so that reporting them is the caller's decision; a library that logs takes that
+  decision away, breaks anything parsing the consumer's stdout, and on a header diagnostic puts a
+  patient's name into whatever collects the logs. One `console.warn` left in during debugging
+  would have shipped, and the only way to find it was to be the person whose output it landed in.
+- Both halves, because neither is enough on its own. A static sweep of `src/` with comments
+  stripped catches a call on a path no test happens to take — the survey table is quoted in
+  comments, so stripping is load-bearing. Running the library with every console method trapped
+  catches one the sweep cannot see, and that was verified rather than assumed: a call written as
+  `globalThis['con' + 'sole'].warn` leaves no literal `console` in the file, passes the sweep, and
+  is caught by the trap.
+
+## 0.4.273
+
+- **Made** the fuzz suite assert the clause it was missing. `tests/README.md` states the safety
+  property in four parts — "it never hangs, never allocates unboundedly, never returns NaN, and
+  never returns believable garbage" — and attributes all four to `property/fuzz.test.ts`, which
+  opened by saying it asserts three and listed them. The gap was "never allocates unboundedly":
+  its bounded clause was a wall-clock budget, which catches slowness, and slowness is a different
+  failure from a corrupt header talking a reader into an allocation it cannot afford.
+- Every fuzz read now runs under `maxMaterializeBytes`, and a read that succeeds must have stayed
+  inside it. Exceeding it throws `EdfBudgetError`, which clause 1 already accepted as a legitimate
+  refusal; the new half is that a decoder which allocated past the ceiling and handed the array
+  back anyway would have satisfied every other clause in the file. Verified by lowering the
+  ceiling below what the fixtures decode to and watching the violation report the byte count.
+
 ## 0.4.272
 
 - **Executed** the offline claim instead of stating it. `tests/README.md` opens with

package/package.json

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