edfcore 0.4.506 → 0.4.508

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.506";
+export declare const VERSION = "0.4.508";
 //# 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.506';
+export const VERSION = '0.4.508';
 //# 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.508
+
+- **Added** an enforcement of the `grid` prefix rule. `migrating-to-0-3.md` explains why three
+  functions were renamed in a minor release, counts the cost — seven separate fixes for one defect,
+  each found because two functions disagreed rather than because one looked wrong — and ends with a
+  naming rule: "you cannot call `gridSampleStartSeconds` and believe you asked for elapsed
+  recording time."
+- A rule that a rename established and nothing enforces lasts until the next function is added, and
+  the next function is the one that would ship the eighth. It is now checked from both sides: every
+  export of the grid module carries the prefix, and no export of the recording-aware module does.
+  The prefix is only a signal if it is exclusive.
+- The reason for the split is asserted rather than described. On the page's own file — a
+  seven-second hole after record 2 — the twelfth sample is at 3 s on the grid and at 10 s in the
+  recording, and on a contiguous file the two calls give the same answer. That collapse is exactly
+  why the difference was easy to miss, so it is stated as a test rather than left as a remark.
+
+## 0.4.507
+
+- **Added** a property test that `readWindow` and `readRecords` agree. They are the two selections
+  the API offers — name a time, or name records — and on a contiguous file a window landing on
+  record boundaries selects exactly the records a caller would have named, so the two must produce
+  the same bytes, sample counts, start and `byteOffset`. Nothing compared them.
+- That is the failure this project has hit repeatedly and names in `whole-api.test.ts`: "a function
+  can be individually correct and still disagree with its neighbour — six releases of this project
+  were exactly that". Each call had its own tests; the pair had none.
+- The window is derived from the records rather than typed, over arbitrary starts and counts and
+  three geometries, two of them with a record duration that is not a whole number of seconds.
+  `readWindow` resolves through `resolveTimeWindow` and `readRecords` does not, so the two reach
+  the same range by different arithmetic — which is the only reason comparing them means anything.
+- The limit is asserted too: half a record in, the window is no longer aligned and `readWindow`
+  returns both records, because a record is the unit the file can be read by.
+
 ## 0.4.506
 
 - **Added** the four-row cost table on `validation.md`, and the claim it exists to support:

package/package.json

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