edfcore 0.6.74 → 0.6.76

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

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.6.76
+
+- **Fixed** the inspector placing each sample at `part.startSeconds + i / rate`, over a rate it
+  derived itself as `samplesPerRecord / (recordDurationSeconds || 1)`.
+- That is mistake 3 on `AGENTS.md` — "Do not compute sample indices from `sampleRateHz`. It is
+  derived and can be `undefined`" — and the reason `sample-grid.ts` exists: "Every viewer needs
+  this and the obvious spelling is wrong." A record duration that does not divide leaves the rate
+  irrational in binary (128 samples over 0.3 s is 426.666…), so the trace walks off its own time
+  axis as `i` grows. The `|| 1` beside it invented a rate for the legal zero record duration,
+  where the library reports none.
+- It now uses `gridSampleStartSeconds`, measured from the chunk's own start so a gap does not
+  shift the trace — each chunk is one contiguous run. The test measures the disagreement on that
+  awkward duration rather than asserting the call.
+
+## 0.6.75
+
+- **Fixed** the inspector deciding whether a file needs a complete index by comparing
+  `spanSeconds` with `coveredSeconds`. `EdfTimeline` says which fields carry that verdict:
+  "`spanTicks === coveredTicks` is the two-probe contiguity verdict, and the ticks are what it
+  must be asked of", because the seconds are float64 conversions and two tick counts can round to
+  one float once the span is large enough that an ulp exceeds a tick.
+- Asked of the floats, such a file answers "contiguous", `buildRecordIndex` is skipped, and the
+  page draws a discontinuous recording on the nominal grid — the silently wrong timeline the
+  library exists to refuse, on the page that is its central claim made checkable. The same
+  comparison was fixed inside `resolveTimeWindow` in 0.3.4 and the type's docblock records it.
+- The test demonstrates the collision rather than arguing it, and shows the two staying apart at
+  an ordinary scale, which is why this could sit there.
+
 ## 0.6.74
 
 - **Fixed** `sample-locate.ts` describing a repeated record onset as something "edfcore reports

package/package.json

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