edfcore 0.4.487 → 0.4.489

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.489
+
+- **Added** a property test for `summarizeDiagnostics`. Everything that prints a count of a file's
+  problems goes through it — the first line of `edfcore validate`, the summary under
+  `edfcore header`, and the `worst` a caller branches on to decide whether a recording is usable —
+  so its one job is to be the list, counted, and every way it can fail is quiet.
+- The existing tests pin the two DECISIONS, which is right: `worst` is by severity rank rather
+  than arrival, and it is `undefined` rather than `'info'` for an empty list. What nothing pinned
+  is that the counting adds up, and that is the part with no decision in it — which is exactly the
+  part nobody writes a case for.
+- Four invariants over arbitrary lists: the three severity counts sum to the length, each equals
+  the number of that severity in the input, `byCode` holds every code once and its counts sum to
+  the total, and it is descending by count with first-seen order inside a tie. The last is what
+  makes two runs over one file diffable, and the docblock promises it.
+- The generator draws from a four-code alphabet on purpose. Unique codes would produce entries of
+  count 1 for ever, and repeats and ties are the whole point — a hand-written fixture reaches
+  neither.
+
+## 0.4.488
+
+- **Added** a property test for `formatDiagnostics`' `maxItems` accounting. The cap is what stops a
+  file with four hundred defects filling a terminal, and the "... and N more" line under the output
+  is the only thing telling a reader that a cap was applied at all.
+- Both ways of getting it wrong are silent. Too small an N and a reader believes they have seen
+  more of the file than they have; a missing line and they believe they have seen all of it.
+- The rounding is where the untested cases were. `resolveLimit` floors a fractional `maxItems`,
+  clamps a negative one to zero, and treats `undefined` and any non-finite value as no cap —
+  four behaviours reachable from a flag, a config file or a caller's arithmetic, each changing
+  what N should be, and none of them a round number anyone writes into a fixture.
+- Three invariants, and the third is what makes the other two mean anything: the blocks shown are
+  the resolved limit, the notice appears exactly when something was withheld, and shown plus
+  hidden is the number that went in. Without the third, showing nothing and claiming everything was
+  hidden satisfies both of the others. Order is pinned separately — a reader who raises the cap
+  expects the lines they already read to still be above the new ones.
+
 ## 0.4.487
 
 - **Set** the suite's test timeout explicitly, at thirty seconds, with the reasoning in the config.

package/package.json

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