edfcore 0.4.522 → 0.4.524

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

package/docs/CHANGELOG.md

@@ -6,6 +6,58 @@ 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.524
+
+- **Added** the six CLI commands over the eight awkward shapes, without the corpus. The CLI is
+  where an unfamiliar file arrives — that is the argument `cli.md` makes for it, "so you can look
+  at a file before writing any code" — and the test that runs it over unfamiliar REAL files,
+  `tests/corpus/cli-corpus.test.ts`, skips on a fresh clone. Offline the commands had been run over
+  `minimalEdf` and `minimalEdfPlus`: two tidy files.
+- Forty-eight invocations, and each must not throw, must not write to stderr on a file that parsed,
+  must print something, must end its last line, and must print no control byte. The shapes are the
+  ones a command can be surprised by: no data signal at all makes `signals` an empty listing and
+  `gaps` a question about a recording that has none, a zero record duration takes the time axis
+  from `gaps` and the rate from `signals`, a duplicate label breaks the one lookup `header` does by
+  name.
+- The exit code is checked against its meaning rather than against a constant. `validate` returns 1
+  for a file carrying an error-severity diagnostic and 0 otherwise — the CI gate the page documents
+  — and a final case asserts the eight shapes produce both codes, or the rule is a constant in
+  disguise.
+- No rendered value may be the word `undefined`, and that needs a precise form: the word appears
+  legitimately in prose, since `ZERO_RECORD_DURATION` says "it makes every sample rate undefined",
+  which is the sentence a reader needs. What is refused is a value SLOT — a field of the
+  tab-separated listing, a leaf of the JSON, the right-hand side of a `label: value` line. Those
+  mean `String(undefined)` reached the output, and a zero record duration is exactly the file that
+  would produce one.
+
+## 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

package/package.json

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