edfcore 0.4.250 → 0.4.252

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

package/docs/CHANGELOG.md

@@ -6,6 +6,27 @@ 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.252
+
+- **Extended** the link check to the repository's own markdown. `README.md`, `AGENTS.md`,
+  `tests/README.md`, `scripts/golden/README.md` and the changelog are read on GitHub rather than
+  built by Astro, so the checks added in 0.4.236 and 0.4.240 never saw them — and they link at
+  source files with ordinary relative paths, which is the form that breaks when a file moves. This
+  repository has already moved one: the changelog was `CHANGELOG.md` until v0.4.1. Every relative
+  target is now resolved against the working tree, and the file list is walked rather than named,
+  so a new `.md` at the root is swept the day it lands. Nothing was broken today.
+
+## 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

package/package.json

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