edfcore 0.4.249 → 0.4.251

package/README.md

@@ -397,7 +397,7 @@ exactly the invention this library refuses. JSR publication.
 
 The full documentation site lives in
 [`website/`](https://github.com/tayal-sarthak/edfcore/tree/main/website), an Astro build with
-22 pages.
+23 pages.
 It includes a **local inspector** that opens an EDF file and shows its header, channels, events
 and waveforms in your browser, with nothing uploaded.
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.251
+
+- **Added** a CLI reference page. The command line had no page of its own: the six commands, the
+  flags, the tab-separated column order and the exit codes lived inside `api-helpers.md`, under a
+  heading two thirds of the way down a page about plotting envelopes and joining chunks. That put
+  the one part of edfcore you can use without writing any code where nothing pointed at it — no
+  sidebar entry, no `llms.txt` line for an agent, and no URL to send anyone. It is now
+  `/docs/cli`, and `api-helpers.md` keeps a pointer where the section was. Its own description no
+  longer claims the CLI either; it lists the text formatters instead, which is what it actually
+  covers.
+
+## 0.4.250
+
+- **Documented the last one.** `EdfAnnotationWindow` is what `filterAnnotationsByTime` takes, and
+  `api-helpers.md` showed the object literal without naming the type or saying why it is not
+  `WindowSelection`: there is no reading here and so no channel to name, which makes it the one
+  window type in the package that never touches a `ByteSource`.
+- **Emptied** `UNDOCUMENTED_TYPES`. It held fourteen exported types when 0.4.220 wrote it down,
+  and six releases took them off — three formatter options, three selections, three envelope
+  results, two BioSemi, two summary, and this one. The title of `docs-coverage.test.ts` has been
+  qualified since 0.4.221 because it had to be; it is plain again. The empty set stays rather than
+  being deleted: it is the seam a future exception would go in, and while it holds nothing the
+  check above it is unconditional.
+
 ## 0.4.249
 
 - **Added** documentation for the two diagnostic summary types, leaving one on the recorded

package/package.json

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