edfcore 0.4.336 → 0.4.338

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

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.338
+
+- **Added** a check that the three published copies of `ByteSource` agree. It is the one type a
+  caller implements rather than consumes — the extension point that lets a file, a blob, an object
+  store and an HTTP range share one path — so it is printed in full on `data-sources.md`, again on
+  `api-sources.md`, and declared in `src/types.ts`. Two of those are hand-typed copies of the
+  third.
+- A drift here is worse than a stale sentence: someone writes an implementation against a printed
+  signature, TypeScript disagrees with the page, and the page is what they trusted. A dropped
+  `readonly`, a `close` that stopped being optional, a `ReadOptions` parameter that gained a
+  sibling — each is a one-word edit that neither `astro check` nor `tsc` can see, because a fenced
+  block is not code either of them compiles. `doc-snippets-compile.test.ts` compiles the fences
+  that are complete programs; this one is a declaration, so it is compared against the declaration.
+
+## 0.4.337
+
+- **Added** an execution of the annotation listing on `quick-start.md`. The page's own format
+  string is transcribed and applied to what `readAnnotations` returns, and it has to reproduce all
+  three printed lines exactly — which catches a `durationSeconds` arriving as `0` instead of
+  `undefined`, since that would print `(+0 s)` on an event with no duration, a different claim
+  about the recording.
+- The docblock states what the check does NOT claim. The fixture is built from the page's own
+  lines, so the onset values vouch for themselves and a page edit changes both sides. Two things
+  are independent of that and are checked as such: the formatting between the numbers, and that
+  every decimal onset survives the round trip as a whole number of ticks, whatever the decimal is.
+- Also pinned: the record range `readAnnotations` requires, which the page says has no default
+  because scanning a whole file for annotations is expensive.
+
 ## 0.4.336
 
 - **Fixed** wrong advice on `quick-start.md`. It said an annotation carries its onset "three ways"

package/package.json

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