edfcore 0.4.488 → 0.4.490

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.488";
+export declare const VERSION = "0.4.490";
 //# 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.488';
+export const VERSION = '0.4.490';
 //# 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.490
+
+- **Added** a check that every published export is reached by the suite a fresh clone actually
+  runs. `tests/corpus/` skips when the corpus is absent — 59 MB of other people's recordings, not
+  redistributed — so those tests do not run on a clone, in CI unless fetched, or for a contributor
+  who has not asked for them.
+- An export whose only appearance in the suite is inside that directory is an export nothing
+  verifies on an ordinary run: it can be renamed, dropped from a barrel or left broken, and the run
+  a contributor does stays green. Not hypothetical here — `whole-api.test.ts` calls essentially the
+  whole barrel and is one of the files that skips.
+- All 78 pass today. The value is the tripwire: adding an export and testing it only against a real
+  file now fails, in the run that would otherwise say nothing.
+- `tests/scratch/` is excluded alongside the corpus for the reason 0.4.479 established — it is
+  gitignored, so anything in it satisfies a check on the machine that wrote it and nowhere else.
+- Deliberately coarse, and the file says so: an import is a floor, not proof the export is called.
+  The floor is the part that can be checked structurally, and it was not being checked at all.
+
+## 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

package/package.json

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