edfcore 0.4.257 → 0.4.259

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

package/docs/CHANGELOG.md

@@ -6,6 +6,38 @@ 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.259
+
+- **Fixed** the snippet in `AGENTS.md` that does not compile. Its "Using edfcore in generated
+  code" section exists to be copied verbatim into somebody's project, which makes it the
+  highest-leverage code in the repository — and it ended `chunks[0].signals[0].digital`, which
+  under `noUncheckedIndexedAccess` is two `error TS2532`s, because both index reads are
+  `T | undefined`. That flag is on in this repo and in every strict TypeScript project, so the
+  file agents are told to copy from was teaching a line the compiler rejects. It narrows now,
+  which is what 0.4.208 settled on for this codebase over a `!`, and the two guards double as the
+  lesson the list right below it already gives: `readWindow` returns an array, and an empty one is
+  an ordinary answer.
+- **Added** the compiled twin. `documented-examples.test-d.ts` has done this for three website
+  snippets since 0.3.46 found two of them rejected the same way; the snippet an agent is likeliest
+  to paste had no such guard. It runs both directions — the copy is real code `npm run typecheck`
+  compiles, and the test reads the fenced block back out of `AGENTS.md` and fails if a line of it
+  is missing here.
+
+## 0.4.258
+
+- **Added** a check on the `Next:` convention, which `AGENTS.md` states as an absolute — "every
+  thrown message ends with a `Next:` clause naming what the caller should do" — and nothing
+  enforced. All 151 messages keep it today; what was missing is that the 152nd would not have
+  had to. The clause is the part that survives contact with a real user: "byte range [0, 512) is
+  outside the 256-byte buffer" says what happened, and "Next: check that the header and these
+  bytes came from the same file" says what it means.
+- Both halves are covered, which took two passes. `EdfFormatError` is never thrown with `new` — it
+  is built from a diagnostic by `fatalError`, `sink.fatal`, `scalingError` and `toFormatError` — so
+  reading only `throw new` sees 90 messages and misses the 61 that carry the larger share of the
+  contract. And finding where a `throw` ends cannot be done by balancing parentheses:
+  `[${offset}, ${offset + length})` closes one, and the first version of this check reported the
+  two messages using that interval notation as violations of a rule they keep.
+
 ## 0.4.257
 
 - **Fixed** `AGENTS.md`'s description of the layering, which had been wrong about nearly every

package/package.json

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