edfcore 0.6.18 → 0.6.20

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.18";
+export declare const VERSION = "0.6.20";
 //# 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.18';
+export const VERSION = '0.6.20';
 //# 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.6.20
+
+- **Added** a thirteenth shape to the `AWKWARD` matrix: a record duration with no exact binary
+  form. `formatHeader` carries the story in a comment beside the function it forced — "100 records
+  of 0.29 s is exactly 29 s and computes as 28.999999999999996, which floors to 28. The header line
+  then reports a recording a whole second shorter than it is (fixed in 0.2.67)."
+- That file is exactly this one, and the matrix had never held it. Every sweep over `AWKWARD` ran
+  on durations of 1 s and 0 s — the two values where the float and the rational agree — so the
+  arithmetic this whole package is written in ticks to avoid was never exercised by any of them.
+  Twenty-three sweeps see it now, and they all pass.
+- `a-duration-float64-cannot-hold.test.ts` spells the hazard out in both directions on the fixture
+  itself: the float product is less than 29 and floors to 28, the tick product is exactly
+  `29n * TICKS_PER_SECOND`, and the header line reads `00:00:29`. It also checks this is the only
+  shape in the matrix whose duration is inexact, and that its derived rate is a clean 100 Hz — an
+  inexact duration does not have to make the rate inexact, and a fixture where both were awkward
+  would not tell the two apart.
+
+## 0.6.19
+
+- **Added** a twelfth shape to the `AWKWARD` matrix: a file whose record count field says `-1`, so
+  the count is recovered from the source length. `types.ts` says of that field "`-1` means the
+  writer never closed the file", and it is not a rare accident — it is what a recorder writes while
+  it is still recording, and what stays there if the software crashes or the disk fills.
+- The recovery itself was covered — `parse.test.ts` for the arithmetic,
+  `one-recording-two-spellings.test.ts` for the equivalence — and the shape had never been put in
+  front of the twenty-two sweeps that run over the matrix: every index resolves, ticks and seconds
+  agree, every array is frozen, nothing points at the caller's buffer, the five source spellings,
+  and the rest. It is the only shape in the matrix whose geometry rests on arithmetic rather than
+  on a number the file states, and each of those sweeps asks a question of a whole file.
+- They all pass over it. That is the result: the properties were stated to hold for any file, and
+  until now none of them had seen one whose record count nobody wrote down.
+- `a-count-the-header-never-gave.test.ts` pins what makes it that shape — `-1` in the field, five in
+  the header, `recordCountSource: 'sourceByteLength'`, and the diagnostic that says so — and checks
+  it is the only shape in the matrix that recovers. A fixture drifting into an ordinary file would
+  otherwise leave twenty-two sweeps looking as though they cover something they no longer do.
+
 ## 0.6.18
 
 - **Fixed** the same thing in the two files 0.6.17 could not see. `README.md` and `AGENTS.md` are

package/package.json

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