edfcore 0.4.274 → 0.4.276

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

package/docs/CHANGELOG.md

@@ -6,6 +6,42 @@ 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.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:
+  `TextDecoder` belongs in `src/tal/` and nowhere else. Verified on Node v24.4.0, every `latin1`
+  label it accepts reports `windows-1252` and decodes byte `0x80` as `U+0080`, while the WHATWG
+  standard mandates `U+20AC` — so a `TextDecoder` on the header path would make the same file
+  produce different strings in Node and in a browser, from a library whose claim is that it reads
+  the same bytes the same way everywhere. `src/tal/` is exempt because annotation text really is
+  UTF-8, the one encoding every runtime agrees on.
+- The stripper removes string literals as well as comments, and that is not tidiness:
+  `header/fields.ts` contains the word `TextDecoder` inside a diagnostic message explaining this
+  rule to a user, so a comments-only sweep reads the file that documents the ban as the file that
+  breaks it. It looked like a live violation until the line was read.
+- A second test asserts the consequence rather than the rule — `0x80` in a real signal label,
+  read back through `openEdf`, comes out `U+0080` and not a euro sign. `latin1.test.ts` pins the
+  decoder in isolation; this is the path a header actually takes.
+
 ## 0.4.274
 
 - **Added** the check that edfcore never writes to the console. The README says it twice, and the

package/package.json

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