edfcore 0.4.457 → 0.4.459

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

package/docs/CHANGELOG.md

@@ -6,6 +6,42 @@ 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.459
+
+- **Added** the two `COMMA_DECIMAL_SEPARATOR` cases that were missing: a comma in the declared
+  header size, and a comma in the record count.
+- `readNumericField` exists for exactly those two fields, because both have an authoritative
+  alternative — the computed header size always wins, and the record count is recoverable from the
+  source length. Both were tested only with values that recover, so the one line in that function
+  which does NOT recover had never run. Deleting it changed nothing visible: the comma fell through
+  to `!parse.ok`, became `NaN`, and was quietly replaced.
+- That silence is what the refusal is for. `"1,024"` in the record count is one thousand and
+  twenty-four records to the writer that wrote it; recovering from the source length yields a
+  plausible number that is right only by accident, and `recordCount` is what every read range in
+  the library is checked against.
+- The contrast is asserted alongside it — any other bad value in those two fields still recovers,
+  with `RECORD_COUNT_RECOVERED` or `HEADER_SIZE_MISMATCH` — so the new cases pin the comma as the
+  exception rather than pinning the fields as fatal.
+
+## 0.4.458
+
+- **Added** tests for a bad HTTP status during a READ, which had never run. `httpSource` reports a
+  status from two places and they are different events: the length probe's "could not read" means
+  the source never existed, and that one was covered; the one inside a read happens on a source
+  that already opened a file, already parsed its header and is part way through a recording.
+- That is the failure this adapter meets most. A signed URL whose expiry passed during a long
+  overnight study, a rotated token, a tightened bucket policy, a 500 from an origin behind a CDN —
+  all of them are mid-read statuses, and the message is written for that reader specifically: it
+  names the byte range being fetched and ends by asking about authentication headers and expiry,
+  neither of which means anything for a URL that never worked.
+- Three statuses are checked because the status is quoted rather than classified. edfcore has no
+  opinion about which 4xx or 5xx means what, and a reader matching the message against an access
+  log needs the number the server actually sent.
+- Also pinned: a failed read leaves no state behind. Without that case, every assertion here would
+  pass on an implementation that latched the first failure and refused every read afterwards —
+  which for a renewed token is the difference between a retry that works and a source that is
+  finished.
+
 ## 0.4.457
 
 - **Documented** `INSPECTION_FAILED` as unreachable today, and added the test that keeps that

package/package.json

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