edfcore 0.4.460 → 0.4.462

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

package/docs/CHANGELOG.md

@@ -6,6 +6,43 @@ 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.462
+
+- **Added** the edge cases for `countOutOfDigitalRange`, the third copy of a rule whose other two
+  copies were already pinned. `decodeInt16` and `decodeInt24` count a sample as out of range only
+  when it is strictly outside `[digitalMinimum, digitalMaximum]`; this copy runs when a trim
+  narrows a chunk that had one, and neither of its comparisons was pinned at the edge. Relaxing
+  either left the suite green.
+- A sample sitting exactly at the declared maximum is the common case, not the exotic one — a
+  saturating amplifier parks a channel at 32767 for the length of an artefact.
+  `outOfDigitalRangeCount` is documented as meaning the declared range is WRONG, so counting a
+  clipped sample says that about the one file where the declaration is exactly right. And only
+  for callers who trimmed: the same samples would be in range before the trim and out of range
+  after it.
+- The inverted declaration is pinned here too. `digitalMinimum > digitalMaximum` is a real writer
+  bug, the decoder compares against min/max of the pair rather than the pair as written, and this
+  copy has to agree — taking them as written makes every sample out of range, again only after a
+  trim.
+- Found by mutation, not by coverage: all three lines were reported as covered.
+
+## 0.4.461
+
+- **Added** the exact-edge cases for `resolveTimeWindow` on a segmented index. The window is
+  half-open — `[start, start + duration)` — and the segmented path decides that on one line:
+  `segmentEndTicks <= windowStartTicks || segmentStartTicks >= windowEndTicks`. Relaxing either
+  comparison to a strict one left the whole suite green, because no window in it had ever landed
+  on a segment edge exactly: they overlapped by a record or missed by ninety seconds.
+- The cost is a duplicated record at every gap. Walking a discontinuous file segment by segment —
+  `[0, 4)` then `[4, 100)` on the fixture here — a relaxed left comparison returns record 3 in
+  both, so a consumer concatenating the two gets one second of signal twice, at the seam where a
+  sleep study is most likely to be scored.
+- Four cases: a segment ending exactly where the window starts is out, a segment starting exactly
+  where the window ends is out, a segment starting exactly where the window starts is IN, and a
+  three-window walk that visits records 0..7 once each. The third is what stops the first two
+  passing on an implementation that excluded every boundary rather than the right one.
+- Found by mutating the comparisons rather than by reading the coverage report, which called the
+  line covered.
+
 ## 0.4.460
 
 - **Added** the fourth rung of `timekeepingDefect`'s ladder, which had never run: a timekeeping

package/package.json

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