edfcore 0.4.251 → 0.4.253

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

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.253
+
+- **Fixed** three stale facts in `AGENTS.md`, which is the first file an agent working on this
+  repository reads and the one nothing verified. It said the suite has "1906 tests" — it has
+  2006, and a count in a file that is not the suite is a number with nothing keeping it honest, so
+  it is gone rather than corrected. It described `npm run check` as "lint + typecheck + tests"
+  when that script has run `build` between them since it was written, which matters because the
+  build is what produces the `dist/` two tests load. And the `scripts/` row now says a release is
+  one commit and needs `-m`, which changed in 0.4.246.
+- **Extended** the committed-fixture check to `AGENTS.md`. It states the "six EDF/BDF files under
+  `corpus/golden/`" claim that 0.4.241 started checking in the two READMEs, and was outside it.
+
+## 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

package/package.json

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