edfcore 0.4.204 → 0.4.206

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

package/docs/CHANGELOG.md

@@ -6,6 +6,25 @@ 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.206
+
+- **Added** a guard that `--help` offers exactly the commands the CLI will dispatch. `cli-run.ts`
+  writes the list twice — as prose in `USAGE`, and as the `COMMANDS` set that refuses a word before
+  the file is opened — and the two fail in opposite directions: one way a command works and is
+  undocumented, the other it is advertised and then rejected as unrecognised. `api-surface.test.ts`
+  compares the *number* of commands in `--help` to the README, so six of one and six of the other
+  passed while naming different things.
+
+## 0.4.205
+
+- **Added** a guard that the four copies of the documentation section list agree. The `z.enum` in
+  `content.config.ts` is written out again in `DocsNav.astro`, `llms.txt.ts` and `llms-full.txt.ts`,
+  and each groups pages by walking its own array — so a name in the enum and not in an array is a
+  section whose pages render at their URL and appear in no index, missing from the sidebar and from
+  both files agents read. DocsNav's docblock says a fifth section "fails the build rather than going
+  missing from the sidebar", which held only while four hand-written lists happened to match, and
+  adding to the enum is the very edit that breaks it. `astro check` sees four well-typed arrays.
+
 ## 0.4.204
 
 - **Corrected** the reason `publish.yml` pins npm. The step said trusted publishing needs

package/package.json

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