edfcore 0.4.495 → 0.4.497

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

package/docs/CHANGELOG.md

@@ -6,6 +6,39 @@ 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.497
+
+- **Added** a test that runs the example on `annotations.md` — the page a reader lands on from a
+  search for how to read EDF+ events. The region's own header fields, the four events a full-file
+  read returns, and what a scan of a 200-record file costs were all prose.
+- The transcript is the part worth having under test. `-0.75 undefined pre-stimulus baseline` says
+  four things at once: onsets are relative to record 0, a negative onset is legal and kept, an
+  absent duration is `undefined` rather than `0`, and the list is sorted by time across record
+  boundaries. Any one of those changing leaves the page describing a library that no longer behaves
+  that way, and none of them is something a reader would think to doubt.
+- The read-cost block goes with it, because it is what the page uses to argue for spelling the
+  record range out at the call site: a full scan of a twelve-hour study is a full download of it.
+  Both rows are checked as one read of the size printed, and against the arithmetic — count records
+  at the record size.
+- Also pinned: a file with no annotations channel returns an empty list with no diagnostics, and
+  still returns the onset grid. That is a whole paragraph of the page and one line of assertions.
+
+## 0.4.496
+
+- **Added** a test that builds and runs the file `api-types.md` documents itself with. That page
+  explains the type surface by showing one recording's values — a six-record EDF+D with a gap,
+  2,328 bytes — across nine separate snippets, and between them they state a byte offset, a byte
+  length, a tick count, a seconds-since-midnight, a sample count and what `locate` returns on both
+  sides of the gap. None of it had been run.
+- `type-tables.test.ts` checks the TABLES on that page: every field a row lists exists on the type,
+  with the type it claims. The snippets between the tables are the other half, and they are where
+  the numbers are. A reader who wants to know what `chunk.byteOffset` means reads `1548`, not the
+  row that says `number`.
+- Nine snippets and one file is what makes it worth building once. The page's internal consistency
+  is itself a claim — `1548` is `768 + 3 * 260`, and each of those three numbers is printed
+  elsewhere on the same page — so the fixture checks the arithmetic BETWEEN the snippets as well as
+  each snippet against the library. Every value is read out of the page.
+
 ## 0.4.495
 
 - **Added** a test that measures the two cost tables on `large-files.md`. That page is the

package/package.json

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