edfcore 0.4.502 → 0.4.504

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.504
+
+- **Added** the values `api-primitives.md` prints beside each primitive. That page is the reference
+  for the layer under `openEdf`, and each entry ends with a line showing what comes back. Six of
+  them say something a reader would otherwise take on trust, and none was executed.
+- Two are contracts rather than examples. `again.buffer === scratch.buffer` is the whole reason
+  `decodeDigital` takes an `out` argument — zero allocations after the first, in a loop over a long
+  recording. And `decodeHeaderLatin1(bytes.subarray(0, 8))` printing `'0       '` with its padding
+  intact is the "no trimming, no interpretation" promise the paragraph above it spends five
+  sentences on: a function that trimmed would satisfy every other test of it, because almost
+  everything else compares a decoded field against its trimmed value.
+- `[ 0, 1 ]` from `findSignals` is the duplicate-label case the page annotates as something CHB-MIT
+  really does, and the reason `getSignal` has an ambiguity error at all. The sentence beside it —
+  the argument is trimmed, the match is case-sensitive, nothing else is normalised — is asserted
+  with it.
+
+## 0.4.503
+
+- **Added** the two snippets on `api-reading.md` that print values — what `openEdf` reports for an
+  eight-hour EDF+C, and what `buildRecordIndex` reports for a file with a one-minute hole — plus
+  the progress contract stated beside them.
+- `documented-read-counts.test.ts` covers that page's read counts. These are the blocks where it
+  prints fields, and they had nothing behind them.
+- The `onProgress` sentences are the part worth pinning, because a caller writes code against them
+  and cannot test them cheaply: "fires once per chunk", and "a file with no annotations signal is
+  not scanned at all … `onProgress` still fires once with the traversal complete, so a progress bar
+  finishes". A bar that stops short is the kind of defect that ships — it looks like slowness, the
+  file is fine, and nothing throws.
+- Dropping either call site now fails a test. Neither did before.
+
 ## 0.4.502
 
 - **Added** a property test for the round trip between `sampleStartTicksOf` and `sampleAt` — the

package/package.json

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