edfcore 0.4.501 → 0.4.503

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.501";
+export declare const VERSION = "0.4.503";
 //# 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.501';
+export const VERSION = '0.4.503';
 //# 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.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
+  pair a viewer uses, a cursor position in and a sample index out.
+- `api-helpers.md` states the rule as a four-way agreement: "`sampleAt`, `sampleStartTicksOf`, a
+  window bound and `readTriggers` all name the same sample." 0.3.32 settled it after `readTriggers`
+  disagreed with the other three, and 0.3.56 moved a window bound onto it after the same mismatch
+  turned up there. Both fixes were made against examples.
+- `sample-grid-roundtrip.test.ts` covers the pure pair, which takes a SIGNAL and knows nothing
+  about gaps. These take the RECORDING, and that is the difference: after a hole a sample's instant
+  is not its index times the interval, so inverting it means finding the segment first. That half
+  was only ever checked at chosen points.
+- Four geometries, two of them with a sample interval that is not a whole number of ticks, each run
+  contiguous and again across a ten-second hole — and once more in ticks rather than seconds, since
+  a trip through seconds can close on rounding luck.
+
 ## 0.4.501
 
 - **Added** the four normalisations `api-sources.md` states for `cachedSource`'s two options:

package/package.json

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