edfcore 0.4.426 → 0.4.428

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

package/docs/CHANGELOG.md

@@ -6,6 +6,47 @@ 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.428
+
+- **Added** a check that a version number which never reached npm says so at the heading and says
+  where its work went. Nineteen of the six hundred-odd headings in this file name a version nobody
+  can install; they exist because a reader comparing `npm view edfcore versions` against the file
+  would otherwise find a hole and be unable to tell a lost number from a missing note.
+- `changelog-continuity.test.ts` checks the sequence. What it cannot see is whether a heading tells
+  the truth about itself, which is the half 0.4.307 was about: fourteen entries had been written
+  before their release failed, so each read exactly like one that shipped, with the correction in a
+  different entry further up that a reader landing on `## 0.4.288` never sees.
+- So the marker has to be first — a note further down is a note nobody scrolling to a version
+  reads — and it has to point forward, because "Never released" alone strands the reader with work
+  that exists under a number they now have to search for. The pointer is bounded at twenty patches
+  and every real one is within six, so an incidental mention of some later release cannot stand in
+  for it: the 0.2.29 entry names 0.4.194 as the release that wrote it down, and that is not where
+  its work went.
+- The two forms are kept apart on purpose. A number consumed before a tag was cut never became
+  public at all; a version that was tagged and whose publish then failed is public on GitHub and
+  absent from npm, which is a different thing to be told.
+
+## 0.4.427
+
+- **Added** a property test for `trimToWindow` against the rule it states rather than the examples
+  it was written from. The source says which samples belong in a window in one line — "Sample j is
+  in the window when `ceil(j * D / S)` is in `[R, Rend)`" — and what the code does is a closed form
+  derived from it: two `floorDiv`s over bigint products, with the derivation written above them. A
+  closed form is exactly where an off-by-one lives, and the derivation is the part a reader takes
+  on trust.
+- So the rule is implemented the obvious way, asking every sample, and the two must select the same
+  set for arbitrary geometries and windows. The naive version is too slow for a library and is
+  obviously right, which is the only pairing worth testing a closed form against.
+- The rounding it turns on is not incidental. 256 samples in a one-second record puts sample 1 at
+  39,062.5 ticks, published as 39,063, and selecting on the exact start rather than the published
+  one excluded that sample from a window beginning at its own published start — half of all indices
+  at that rate, and at 128 samples per 0.29 s a one-sample window came back empty (0.3.56).
+  Geometries whose boundaries miss whole ticks are generated deliberately, because the ones that
+  land on them cannot tell the two rules apart.
+- Three obligations from the docblock come with it, none previously checked in general: adjacent
+  windows partition a chunk exactly, a window covering the chunk is the identity, and the result is
+  a view rather than a copy.
+
 ## 0.4.426
 
 - **Added** a property test that the cache is invisible at every size it can be configured to.

package/package.json

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