edfcore 0.4.521 → 0.4.523

package/README.md

@@ -77,7 +77,7 @@ for (const event of annotations) {
 }
 ```
 
-> **Status: 0.4.x, early.** edfcore runs 2,500+ tests on generated fixtures, and it's checked
+> **Status: 0.4.x, early.** edfcore runs 2,700+ tests on generated fixtures, and it's checked
 > against public corpora it didn't author: the EDF, EDF+ and 24-bit BDF+ test files from
 > teuniz.net, and PhysioNet's sleep-edfx (a real 22-hour polysomnography recording and its
 > sleep-staging file). Those checks are numeric. Channels labelled `sine 8.5 Hz` decode to

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

package/docs/CHANGELOG.md

@@ -6,6 +6,59 @@ 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.523
+
+- **Fixed** a vacuous assertion in `inspect-safety.test.ts`, the property test for the strongest
+  promise in the package. It read `header.signals.length` against
+  `header.signals.filter((signal) => signal !== undefined).length` — a `readonly EdfSignal[]` has
+  no holes, so the filter drops nothing and the line compared a number with itself.
+- It is the same line, in the same words, that `whole-api.test.ts` carried until 0.3.101, where its
+  own docblock records finding it. The copy here outlived the fix by four hundred releases, and it
+  was the one line in the file claiming to check that a report is internally coherent rather than
+  merely present.
+- In its place are the four consistency claims the corpus test now makes, and here they run over
+  damaged bytes rather than six real files: the two index arrays partition the signals (each is
+  data or annotations, none is both, none is missing from both), each signal's `index` is its
+  position, the reported `headerByteLength` is the one its own signal count implies, `ok` is
+  exactly "no error-severity diagnostic", and `bytesRead` exceeds neither the file nor the 128 KiB
+  ceiling. All of them hold today under bit flips, truncation at every length, and uniformly
+  random bytes.
+- Everything from `header !== undefined` onwards is skipped when triage could not parse one, and
+  random bytes almost never produce one — so the run now counts how many reports came back with a
+  header and asserts the count. A run that got past that line zero times would report green having
+  checked only that nothing threw, which is how the assertion it replaces survived.
+- The suite-size figure moves from 2,500 to 2,700, in the three places that state it — the README's
+  status line, the foot of `installation.md`, and the docblock of `browser-safety.test.ts`. The
+  tests added over 0.4.520-0.4.522 pushed the written-out count past it, which is the direction
+  `test-count-claims.test.ts` exists to catch: "N or more" stays true forever once it is true, so
+  the property that makes it safe is the property that makes it worthless. It refused the release
+  rather than letting the number quietly describe a smaller repository.
+
+## 0.4.522
+
+- **Added** the reading/scaling/decimating agreement checks to the offline suite — the third group
+  in `tests/corpus/whole-api.test.ts`, which skips without the corpus. These are four calls a
+  viewer makes in sequence: read a window, join the chunks, convert to units, draw a decimated
+  envelope. Each can be individually right while contradicting the one before it.
+- The envelope is where that bites. `readEnvelope` reads and reduces on its own path rather than
+  decimating what `readWindow` returned, so its extremes and the samples' extremes are two
+  independent answers to the same question about the same window, and only comparing them says
+  they agree.
+- Running it on built files covers more than running it on real ones. The shapes include a file
+  with no data signal at all and one with a zero record duration, where the honest answer to "read
+  a window of it" is nothing — and a helper that returns nothing where its neighbour throws is
+  exactly the disagreement this group exists to find. The corpus reaches those shapes by luck.
+- Every case returns early on a file it cannot apply to, so the file ends by asserting how many
+  times it got through: windows read, envelopes compared, samples located. Without that the whole
+  run could return early and report green.
+- The **annotation-helper** group lands with it, since it is the same argument about a different
+  four calls: a census, a text filter, a formatter and two time lookups, all describing one list.
+  Each is asked about every event's OWN onset, which puts every event on the boundary of the
+  half-open interval it is being looked for in rather than hoping one lands there — and half-open
+  boundaries are where five of the comparisons this project has had to fix went wrong. Four of the
+  eight shapes carry no annotations channel, and two empty lists agree about everything, so that
+  file also counts the events it reached.
+
 ## 0.4.521
 
 - **Added** the timeline-helper agreement checks to the offline suite, the second group in

package/package.json

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