edfcore 0.5.45 → 0.5.47

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

package/docs/CHANGELOG.md

@@ -6,6 +6,45 @@ 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.5.47
+
+- **Added** the transformation of appending bytes after the last record: exactly one diagnostic, and
+  nothing else moves. `header-recovery-advice.test.ts` covers what the two codes claim — that the
+  extra bytes are never decoded and that reaching them by record number is refused. Nothing covered
+  the transformation itself.
+- It matters because the recovery is arithmetic on the file's length. `parseHeader` computes the
+  record count the file can actually hold and compares it with the declared one, so a change in
+  length reaches `recordCount`, `dataByteLength`, the timeline and everything derived from them.
+  Getting the recovery right and the arithmetic around it wrong would look, from any single
+  assertion, like the recovery working.
+- The boundary is checked at the byte. Fewer bytes than a record is `PARTIAL_FINAL_RECORD` — a
+  writer that stopped mid-record. A whole record's worth or more is `TRAILING_BYTES` — something
+  else appended after a complete file. One byte either side of `recordByteLength` decides which, and
+  edfcore never reports both.
+- Everything else is compared against the untouched file at six append sizes: the samples of every
+  record, the annotations and the record onsets, `recordCount`, `dataByteLength`, `spanSeconds` and
+  `coveredSeconds` — and the header and a full validation sweep each gain exactly one code and lose
+  none.
+
+## 0.5.46
+
+- **Added** the same recording cut into records four different ways. "The record is the unit of I/O,
+  never the channel" is a heading in `design-decisions.md` and the premise of `concepts.md`. The
+  corollary is what a caller has to believe and nothing checked: the record geometry is a property
+  of how the file was written, and it decides the cost and the shape of a read while deciding
+  nothing about the signal.
+- A writer with 128 samples at 16 Hz may store them as 8 records of 16 at one second each, or 16 of
+  8 at half a second, or 2 of 64 at four seconds. Those are four different files — different record
+  size, different count, `recordByteLength` from 96 to 208 bytes — and one recording. All four are
+  built and compared: the sample stream over the whole file is identical, and so are `sampleRateHz`,
+  `signal.sampleCount` and `timeline.spanSeconds`, none of which is stored and all of which are
+  derived from the geometry that differs.
+- The window is what makes this a test rather than a paragraph. Asking for `[1.25, 3.75)` — inside a
+  record in all four — returns four **different** chunks: record 1 plus 3 in one file, record 0 plus
+  1 in another, because a read is record-aligned and the records are not the same size.
+  `trimToWindow` then gives the same 40 samples starting at 1.25 s in every one of them. That is the
+  architecture in one comparison: the chunk is the I/O and the trim is the answer.
+
 ## 0.5.45
 
 - **Added** the relationship between `inspectEdf` and the call it is triage for. `diagnostics.md`

package/package.json

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