edfcore 0.4.509 → 0.4.511

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

package/docs/CHANGELOG.md

@@ -6,6 +6,45 @@ 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.511
+
+- **Fixed** `physical-values.md` documenting the limitation 0.4.509 removed. Its note said a fifth
+  refusal condition exists, that the header calls it `DEGENERATE_PHYSICAL_RANGE`, and that
+  `toPhysical` "can't re-derive this one" so it throws `SCALE_UNAVAILABLE`. The last clause stopped
+  being true one release ago.
+- The page's table now lists five conditions rather than four, so the fifth is documented where a
+  reader looks for it rather than in an aside below. Five rows, four distinct codes: two conditions
+  reach `DEGENERATE_PHYSICAL_RANGE`, which is why the table is of conditions.
+- The table is not prose. `scaling-page-arithmetic.test.ts` parses these rows out of the page and,
+  for each, builds the signal and asserts `toPhysical` refuses it with the code in that row — so
+  the new row is checked by the same mechanism as the other four, and the page cannot describe a
+  refusal the library does not make. The order it claims is checked too: a channel that is both
+  log-transformed and unusably scaled is refused as the log-transformed one, which is the answer
+  that says something about the data rather than about the map.
+- The note is kept, rewritten as history: what the two sides used to report, and why looking up
+  `SCALE_UNAVAILABLE` in `header.diagnostics` used to find nothing.
+
+## 0.4.510
+
+- **Added** the one claim every diagnostic makes at once, as a property test: `raw` quotes the
+  bytes `byteOffset` names. `EdfDiagnostic.raw` is documented as "those bytes as text, exactly as
+  written including padding" — the bytes AT the offset the same diagnostic reports — and it is the
+  only evidence a reader has that a diagnosis is about the field in front of them.
+- It had gone wrong three times, three different ways, each found by eye rather than by a test:
+  0.3.26, where `NON_ASCII_HEADER_FIELD` quoted bytes contradicting its own claim; 0.3.68, where a
+  TAL diagnostic put the escaped message preview in `raw` and returned a 13-character string for
+  four bytes; and 0.3.73, where `PARTIAL_FINAL_RECORD` pointed into the data section while carrying
+  the record-count field's eight bytes. Nothing checked the pair, which is how one defect appeared
+  in three places.
+- Both sides are damaged at random and checked, because they derive the offset differently: a
+  header field's comes from a fixed table, a TAL's is recomputed as
+  `headerByteLength + recordIndex * recordByteLength + signal.recordByteOffset` while the bytes are
+  sliced from a record buffer that starts at neither. Dropping the last term of that sum, or adding
+  one to a header field's offset, each fail the run.
+- Roughly 15,000 diagnostics across 24 codes satisfy it today, and the run asserts the counts as
+  well as the property: a change that stopped producing diagnostics under damage would otherwise
+  pass by having nothing to check.
+
 ## 0.4.509
 
 - **Fixed** `toPhysical` naming a different cause than the header for one class of unscalable

package/package.json

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