edfcore 0.4.335 → 0.4.337

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.335";
+export declare const VERSION = "0.4.337";
 //# 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.335';
+export const VERSION = '0.4.337';
 //# 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.337
+
+- **Added** an execution of the annotation listing on `quick-start.md`. The page's own format
+  string is transcribed and applied to what `readAnnotations` returns, and it has to reproduce all
+  three printed lines exactly — which catches a `durationSeconds` arriving as `0` instead of
+  `undefined`, since that would print `(+0 s)` on an event with no duration, a different claim
+  about the recording.
+- The docblock states what the check does NOT claim. The fixture is built from the page's own
+  lines, so the onset values vouch for themselves and a page edit changes both sides. Two things
+  are independent of that and are checked as such: the formatting between the numbers, and that
+  every decimal onset survives the round trip as a whole number of ticks, whatever the decimal is.
+- Also pinned: the record range `readAnnotations` requires, which the page says has no default
+  because scanning a whole file for annotations is expensive.
+
+## 0.4.336
+
+- **Fixed** wrong advice on `quick-start.md`. It said an annotation carries its onset "three ways"
+  and then named `onsetSecondsFromFirstRecord`, `onsetSecondsFromHeaderStart` and `onsetTicks` —
+  one float from each axis and a bigint from only one of them — closing with "Print the seconds;
+  compare the ticks." Followed literally on a file that declares a sub-second start offset, that
+  prints the rebased seconds and compares the header-axis ticks: on a 0.5 s offset, an event shown
+  at 1.25 s and tested at 1.75 s, silently.
+- There are four fields, two per axis, and `annotations.md` has had them right in a table all
+  along. The quick start now names both members of both pairs, keeps the "print the seconds,
+  compare the ticks" advice with "from the same axis" attached, and says what the two axes differ
+  by. Checked on a file with an offset and again on one without, where the two collapse — which is
+  why this was easy to miss.
+- This is the same shape as the defect the rename in 0.3.0 exists to prevent: two quantities that
+  agree on an ordinary file and part company on the one that matters.
+
 ## 0.4.335
 
 - **Added** a check over the console output `quick-start.md` prints. Between two `text` blocks the

package/package.json

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