edfcore 0.4.265 → 0.4.267

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

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.267
+
+- **Added** a check that the column table on the CLI page is the order `edfcore signals` emits.
+  That command exists to be piped into `awk`, so its columns are a positional contract, and two
+  places stated it: the table on `cli.md`, and `cli.test.ts`, which pinned it against a hard-coded
+  array. Neither knew about the other, so a column inserted rather than appended could be made to
+  pass by editing the test while the page went on describing the old layout to everyone parsing
+  it. Not hypothetical: column 6 was appended in 0.2.42 precisely so nothing reading the first
+  five by position would move, and before that the page claimed the command emitted samples per
+  record where it emitted `kind`, with the authoritative field in no column at all.
+- The expectation is read from the page, and the fixture gives every column a distinct value — a
+  two-second record of fifty samples, so the rate is 25 and the count is 50 — because two columns
+  holding the same number would let a transposition through.
+
+## 0.4.266
+
+- **Added** a check that every `npx edfcore …` written in the documentation is one the CLI
+  accepts. The commands were checked two ways already and neither covered it: `api-surface.md`'s
+  count is compared with `--help`, and `cli-command-list.test.ts` asserts `--help` offers exactly
+  what the dispatch switch handles. Both compare the CLI with itself. The sixteen invocations
+  spread across the README, the CLI page and the guides — the lines a reader actually copies into
+  a terminal — were checked by nobody, and renaming a command is exactly the change that would
+  leave both existing checks green while every page still named the old one.
+- Driven through `runCli` rather than `parseArgs`, because an unknown command is not a parse
+  error: `parseArgs` puts any non-flag word in the command slot quite happily, so checking the
+  parser would have passed on `edfcore summary`. Exit code 2 is the documented contract for bad
+  usage, and that is what this asserts against.
+
 ## 0.4.265
 
 - **Added** the unit test `printable` never had. It is the smallest module in the package and its

package/package.json

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