edfcore 0.4.497 → 0.4.499

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.499
+
+- **Added** the scaling contract as `concepts.md` states it: `signal.scale` is `undefined`,
+  `toPhysical` throws, and `decodeDigital` still works. Three lines that are the package's central
+  refusal rather than an illustration of it — the page names what the reference implementation does
+  instead, which is to substitute a gain of 1 and return ADC counts labelled as microvolts.
+- `physical-values.md` has its own arithmetic test and `scale.ts` has unit tests for each
+  condition. What nothing checked is the trio together on one signal, which is what a reader takes
+  away from the page: the samples are real and keep working, and it is the interpretation that is
+  unavailable.
+- The four conditions the paragraph lists are checked as a closed list, because a fifth appearing
+  without the sentence changing is the drift worth catching, and that sentence is what a reader
+  plans around.
+- The diagnostics block is the other closed list on that page — five properties, one per producer.
+  All five are now exercised and compared against the list parsed out of the page, so a sixth
+  producer, or a renamed property, fails here.
+
+## 0.4.498
+
+- **Fixed** an error message quoted on two documentation pages that no version of edfcore has been
+  producing. `concepts.md` and `discontinuous.md` both print the `RangeError` you get for asking a
+  time question of a probed index, and both quoted it as "a probed index knows where neither the
+  gap nor the records after it start" — the library says "the discontinuity", and has since the
+  wording was narrowed.
+- Both were also missing a whole clause. The real message ends "Exactly: 160000000 against
+  60000000 ticks of 100 ns" before its `Next:`, and that sentence exists because the two second
+  counts in the clause above it can PRINT the same on a long recording. The pages had dropped the
+  one clause that makes the message actionable in the case it was written for.
+- Rewording an error is a small edit in a different file, which is why a quotation of one rots.
+  Found by running the walk-through rather than by reading it.
+- **Added** the rest of that walk-through as a test: the probed index admitting what it has not
+  seen, the span and coverage that differ, the two segments and one gap a scan finds, and the two
+  chunks the same `readWindow` call becomes once it has an index — with `precededByGap` on the
+  second and not the first.
+
 ## 0.4.497
 
 - **Added** a test that runs the example on `annotations.md` — the page a reader lands on from a

package/package.json

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