edfcore 0.4.523 → 0.4.525

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

package/docs/CHANGELOG.md

@@ -6,6 +6,49 @@ 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.525
+
+- **Added** a check that what the CLI prints is what the library reports, over the eight awkward
+  shapes. 0.4.524 checks the six commands survive them; surviving is not agreeing, and a command
+  that caught its own exception and printed a plausible summary would pass that while being worse
+  than a crash — the output is what a reader pastes into an issue.
+- Three commands carry values rather than prose, and each is re-derived from the library and
+  compared. They rot differently. `json` is read by scripts, so a field that quietly stops matching
+  the header is acted on rather than noticed. `events` prints a count and then a listing, which can
+  disagree with each other as well as with the file. `gaps` runs its own full scan — deliberately,
+  since the probed index cannot see a gap in the middle — so its numbers come from a second
+  traversal that nothing had compared with the first.
+- The `json` case pins the shape a zero record duration produces: `JSON.stringify` drops a key
+  whose value is `undefined`, so an absent sample rate is an absent KEY rather than a null, and the
+  test asserts the key is present exactly when the rate is. `--patient` is checked to print the raw
+  field with padding trimmed, and its absence to be a missing key rather than an empty string.
+- `signals` is not here — `cli-signals-columns.test.ts` ties all six of its columns to the header
+  already, which is this check in the same shape.
+
+## 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

package/package.json

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