edfcore 0.4.494 → 0.4.496

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.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
+  random-access claim made concrete — it names two files by their exact geometry and prints, byte
+  for byte, what opening one and reading ten seconds out of the other costs. Four read ranges with
+  their offsets, two totals, a percentage, a sample count, an overread factor, and the highest byte
+  either read touches. None of it had ever been run.
+- `documented-read-counts.test.ts` checks the read COUNTS `api-reading.md` states in prose. This
+  page states offsets and lengths, which is the stronger claim and the one a reader budgets
+  against: an HTTP round trip is priced by where a range starts and how long it is, not by how many
+  there are.
+- Neither file is built. One is 29 MB and the other 442 MB, and both claims are about which bytes
+  are ASKED for, so a source that reports the length, serves a header of the right geometry and
+  records the ranges answers it exactly.
+- Every figure comes out of the page, so the two cannot drift apart in either direction. All of
+  them hold: the four open reads land on the offsets printed, the ten-second window is one
+  153,600-byte range at 221,191,936, and the far end of the recording is never addressed.
+
 ## 0.4.494
 
 - **Added** a test that produces the refusal `large-files.md` prints. That page's budget section is

package/package.json

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