edfcore 0.4.412 → 0.4.414

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

package/docs/CHANGELOG.md

@@ -6,6 +6,43 @@ 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.414
+
+- **Added** a check that binds every entry of AGENTS.md's "Things that look like bugs and are not"
+  to the test that pins it. The section exists because each entry is something a reader improves on
+  sight — the scaling expression has an obviously better rearrangement, `readWindow` returning an
+  array for a continuous file is an obviously unnecessary wrapper, an optional `signal.scale` is an
+  obviously missing default — and every one of them has been proposed.
+- It closes with a promise about itself: "Each of the code rules has a test pinning it and a comment
+  explaining why." Nothing checked that sentence, and both ways it stops being true are ordinary. A
+  rule gets added because someone was bitten by it and no test comes with it, so the list reads as
+  enforced while it is not. Or a test is renamed in a tidy-up, and nothing fails — the rule is still
+  checked, or it is not, and nobody can tell which from the list.
+- The binding is checked in both directions: a new bullet with no entry fails, and an entry naming
+  a file that no longer exists or no longer mentions the rule fails too. Each binding carries a
+  phrase the file must contain, so a filename alone cannot stand in for a check.
+- The last entry is exempt by the sentence's own words — it is a fact about a branch on a remote,
+  which an offline suite cannot see — and it is required to still BE the last, because a rule
+  appended after it would inherit an excuse written for something else.
+
+## 0.4.413
+
+- **Added** tests for the calendar edfcore validates against. `isValidCalendarDate` exists because
+  a `Date` is the wrong tool: real files carry 31 April and 29 February in common years, and
+  `new Date(1997, 3, 31)` rolls both forward into a neighbouring month rather than rejecting them.
+  A recording silently dated a day later than it was made is the kind of error nobody finds,
+  because the wrong answer is a perfectly ordinary date.
+- `date-ban.test.ts` proves no `Date` is constructed anywhere. That left the arithmetic which
+  replaced it, exercised only through the parser, where a rejected date is indistinguishable from a
+  rejected field.
+- The month lengths are not restated — restating a table checks a transcription, and the
+  transcription is what would already be wrong. The properties it must satisfy are checked instead,
+  from the Gregorian calendar rather than from this file: the twelve months sum to 365 or 366 for
+  every year from 1 to 9999; four hundred consecutive years hold exactly 97 leap years and 146,097
+  days, which is a whole number of weeks; and a century not divisible by 400 holds 24, not 25.
+- A table with a month a day short fails the first for every year, and a leap rule missing its
+  century exception fails the second by three days a cycle.
+
 ## 0.4.412
 
 - **Added** tests for four header fields that are all finite and imply a gain that is not. An EDF

package/package.json

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