edfcore 0.4.300 → 0.4.302

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

package/docs/CHANGELOG.md

@@ -6,6 +6,33 @@ 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.302
+
+- **Made** `api-reading.md`'s read counts the expectation rather than a second statement of it.
+  "On a plain EDF or BDF it costs two reads. On a file that carries an annotations signal it costs
+  four. A single-record file is probed once, for three reads total" is the random-access claim in
+  miniature, and the number a reader budgets an HTTP round trip against.
+  `read-pattern.test.ts` already pins those counts — against literals it holds itself, so the page
+  and the suite each stated the contract and nothing compared them.
+- The numbers are parsed out of the sentence and each case driven through the counting source,
+  including the one the page states without a number: a file with no data records is not probed at
+  all, so it costs the plain count. Spelled-out numbers are read through a word list, the same
+  treatment the fixture counts get, because prose is the right place for them to be words.
+
+## 0.4.301
+
+- **Executed** the worked example on `concepts.md`, the page the site opens with and the README
+  calls "the mental model the rest of the API follows from". It is built almost entirely out of
+  arithmetic on one described file — a 768-byte header, thirty 544-byte records, 17,088 bytes
+  total, and a ten-record read of the narrow channel costing 5,440 bytes for 160 samples — and
+  every number was prose. A reader who works through it and gets a different answer from their own
+  file has no way to tell which of the two is wrong.
+- All of them are correct. What was missing is anything keeping them so: they follow from
+  `headerByteLength = 256 * (signals + 1)` and the record layout, and a change to either would
+  leave the page teaching the old ones. The fixture is built to the page's description with the
+  suite's own writer, which imports nothing from `src/`, so the numbers are checked against a file
+  assembled from the specification rather than against edfcore's idea of one.
+
 ## 0.4.300
 
 - **Executed** the claim the error API is shaped around. `src/errors.ts` says class identity is

package/package.json

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