edfcore 0.3.84 → 0.3.86

package/CHANGELOG.md

@@ -6,6 +6,42 @@ 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.3.86
+
+- **Fixed** `formatStartTimeNaive`'s reference entry naming one of its two `undefined` cases, and
+  naming it as an equivalence: "Returns `undefined` when `startTime.resolvedDate` is `undefined`,
+  i.e. the file carries no resolvable date."
+  - It also returns `undefined` when `startTime.clockSource === 'none'` — the `hh.mm.ss` field
+    failed its grammar, so `startTime.clock` is a substituted midnight and there is no instant to
+    render. That case was added deliberately in 0.3.17, because a file whose starttime reads
+    `23.59.60` otherwise came back as `...T00:00:00.000`: a wall-clock instant the file never gave,
+    and for a sleep study the most believable start there is.
+  - `validation.md` and the source docblock both state it. The function's own reference page did
+    not, so a caller who checked `resolvedDate` first — exactly what the "i.e." invites — still got
+    `undefined` and had nothing to look up.
+- The entry now lists both conditions in a table and says which release added the second. The guard
+  checks the page names both **and** exercises the behaviour on a `23.59.60` file, so the page is
+  pinned to the code rather than to itself.
+
+## 0.3.85
+
+- **Fixed** four pages denying a comparison the test suite performs on every run.
+  - `api-primitives.md` — the page a caller reads to decide whether to trust the pinned scaling
+    expression — said the float64 parity with pyEDFlib "isn't yet demonstrated by a golden-value
+    harness, so treat it as intent rather than a measured guarantee". `api-validate.md` and
+    `validation.md` said edfcore's output "has not been compared element by element" against
+    pyEDFlib or MNE. `comparison.md` said validation against the public corpora "has not happened
+    yet".
+  - `tests/corpus/golden-values.test.ts` writes its fixtures with pyEDFlib's own writer, reads them
+    back with pyEDFlib, and compares every physical sample against the IEEE-754 bits it produced
+    using `Object.is` — a one-ULP difference fails. `mne-parity.test.ts` does the same for MNE. The
+    goldens are committed, so both run on a fresh clone. The harness has existed since 0.2.34-0.2.48.
+  - The pages now say what is measured and what is not, and `comparison.md` says plainly that the
+    corpus tests SKIP without `npm run corpus:fetch` — so a fresh clone proves the golden comparison
+    and not the corpus one. Understating a guarantee is still a false statement about the package.
+- Same class as 0.3.64, which removed this wording from three other pages and missed these four. The
+  guard now sweeps every page for both retired phrasings.
+
 ## 0.3.84
 
 - **Fixed** four statements that the `node:` import lives in exactly one file. `src/cli.ts` imports

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

package/package.json

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