edfcore 0.4.275 → 0.4.277

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.277
+
+- **Fixed** a test budget that has now been wrong twice, by making it a different kind of number.
+  `extreme-geometry.test.ts` asserts that a diagnostic per record does not blow the call stack —
+  `TIMEKEEPING_TAL_MISSING` is per record, and `push(...array)` gives up around 125,000 arguments
+  — and it carried a 30 second timeout. How long the sweep takes is not the property. A timeout
+  set just above the observed duration measures the machine instead of the code, and reports a red
+  build in something the test does not touch.
+- It started at vitest's 5 second default, which the 200,000-record sweep landed a few hundred
+  milliseconds under on its own, so it tipped over whenever the rest of the suite ran beside it.
+  Thirty seconds fixed that and repeated the mistake one size up: the suite kept growing — 2,074
+  tests now, one of which spawns a TypeScript compiler over 102 files — and on a machine already
+  busy with unrelated work the sweep took 72 seconds and failed again. It is five minutes now, and
+  named for what it is: an infinite loop still fails, a loaded laptop does not.
+
+## 0.4.276
+
+- **Added** the check for the other ban `AGENTS.md` lists: "No `Date` anywhere. EDF stores local
+  time with no zone." An EDF header gives a wall-clock date and time and names no zone, because
+  the machine that wrote it was in a sleep lab and the field is whatever the clock on the wall
+  said. A `Date` cannot hold that — constructing one applies the running machine's zone, so a
+  recording started at 23:14 in Leiden becomes a different instant on a laptop in California and
+  every derived time moves with it. `EdfCalendarDate` is three numbers precisely so there is
+  nothing to interpret.
+- Two halves, and only one existed. `dates.test.ts` asserted a parsed HEADER holds no `Date`;
+  this adds the source, where `Date.now()` would also make output non-deterministic, and a deep
+  sweep of a whole read — recording, timeline, index, annotations, validation report — for any
+  `Date` instance at all.
+- **Extracted** the comment-and-string stripper both bans need into
+  `tests/support/code-only.ts`. It was written for 0.4.275 a release ago, and a second copy is how
+  the barrel type parser ended up with two that disagreed (0.4.224). Stripping strings is the part
+  that matters: this codebase discusses dates constantly, and a file explaining why it avoids
+  `Date` must not read as a file that uses one.
+
 ## 0.4.275
 
 - **Added** the check for a ban `AGENTS.md` lists under things that look like bugs and are not:

package/package.json

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