edfcore 0.4.334 → 0.4.336

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.334";
+export declare const VERSION = "0.4.336";
 //# 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.334';
+export const VERSION = '0.4.336';
 //# 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.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
+  page pins the whole shape of a read — variant, record geometry, three channels with their kinds
+  and sample counts, and `2560 samples, 6040 bytes read` — and the fixture is now built from the
+  block's own description of the file rather than from a fixture that happens to resemble it.
+- The byte count is the number worth holding. The page stops to explain that 6040 "is more than
+  the 5120 bytes those 2560 samples occupy", because a record is the smallest readable unit and
+  every channel is interleaved into it — so the overhead a reader budgets from this page follows
+  from the annotation channel's width, three lines further up the same block. That subtraction is
+  checked, not just the total.
+- The individual sample values are deliberately not checked. They come from a recording nobody
+  here has, and a fixture reproducing them would be asserting against its own generator.
+
 ## 0.4.334
 
 - **Added** a check over the `validateHeader` table on `api-validate.md`, which was one of the four

package/package.json

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