edfcore 0.6.46 → 0.6.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.6.46";
+export declare const VERSION = "0.6.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.6.46';
+export const VERSION = '0.6.47';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ 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.6.47
+
+- **Fixed** a claim in `api-primitives.md`: that when a header declares more records than the file
+  holds, "the difference between those two numbers is the only evidence" of a truncated download.
+  A writer that flushes its record-count field as it goes — so a reader can follow the recording —
+  and then dies mid-record leaves a file whose declared count equals the whole records on disk,
+  with a fraction of one more after them. There is nothing to subtract.
+- `header/parse.ts` already handles it: `declared === wholeRecords` with bytes left over reports
+  `PARTIAL_FINAL_RECORD` rather than `TRAILING_BYTES`, because a partial record is not spare bytes.
+  `recordCount` is unaffected and `recordCountSource` stays `'headerField'`.
+- The matrix shape that hid it is `a download that stopped part way`, which earns `TRUNCATED_FILE`
+  and `PARTIAL_FINAL_RECORD` together — so the second code never appeared on its own, and the
+  sentence about the first looked like it covered both. A test now builds the file where it does.
+- The page keeps its point, which was never in doubt: both findings need `sourceByteLength`, and a
+  header-only buffer looks like a complete file whose records all happen to be missing.
+
 ## 0.6.46
 
 - **Changed** the `Next:` clause of `DATE_CLIPPED_TO_1985_2084`, which could not be followed on any

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.46",
+  "version": "0.6.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.6.46';
+export const VERSION = '0.6.47';