edfcore 0.4.301 → 0.4.303

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

package/docs/CHANGELOG.md

@@ -6,6 +6,31 @@ 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.303
+
+- **Executed** the request budget on `api-sources.md`: one `HEAD` for the length, `bytes=0-255`,
+  one more range for the rest of the header, and one whole record at each end for the timekeeping
+  probes — five in total, with the caller's headers on all five. That is the paragraph a reader
+  consults before pointing this at S3, and every clause is a cost they are budgeting.
+- The count was pinned elsewhere against a literal; the composition was prose, and so was the
+  promise about headers — the clause with a security shape, since one request quietly going out
+  without the configured `Authorization` 403s in production and nowhere else. All of it is now
+  driven through an injected `fetch`, which the suite requires of anything touching the network
+  and which is also how the page tells a reader to test their own adapter.
+
+## 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

package/package.json

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