edfcore 0.4.405 → 0.4.407

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.407
+
+- **Added** tests for a window over a recording whose records do not advance in time.
+  `concepts.md` calls a zero record duration legal and says what edfcore does about it — a
+  `ZERO_RECORD_DURATION` warning, `sampleRateHz` left `undefined`, "and keeps reading" — and
+  `api-errors.md` names the shape it comes from: an annotations-only EDF+ recording, whose records
+  carry events and no samples.
+- "Keeps reading" is the part with a window in it. Every record sits at one instant, so a window
+  either contains that instant or it does not and there is no interval arithmetic to do. That is
+  why the code has a separate branch for it, and why that branch is where a division by zero would
+  otherwise live. Both index shapes carry their own copy — a complete index answers from its
+  segments, a probed one from the nominal grid — and the two are now required to agree on every
+  window put to them.
+- The boundary rule is the same as everywhere else: a window opening exactly on the instant
+  contains it, one closing exactly on it does not.
+
+## 0.4.406
+
+- **Added** tests for the index `validateRecording` is handed, and whether it is allowed to answer
+  for the file. `api-validate.md` describes the option as a complete index "whose onsets the sweep
+  reuses instead of reading them again", and nothing checked what happens when the index does not
+  fit.
+- That is an ordinary mistake — a viewer holding indices for several open recordings, a helper that
+  caches one per session, a loop that forgets to rebuild — and the consequence is not a wrong number
+  but a wrong file: the segments and gaps of recording A reported as the structure of recording B,
+  in a report whose whole purpose is to say whether *this* file conforms.
+- The rejection is checked by observation rather than by reading the guard. A rejected index makes
+  the sweep read the onsets itself, so a spy counts it, and the cost is required to equal passing no
+  index at all — which is what "ignored" has to mean.
+- Also covers `DISCONTINUITY_IN_CONTINUOUS_FILE` on a file that both skips and repeats time. Gaps
+  travel in one array partitioned by sign, an overlap being an entry with a negative duration
+  (0.2.69), and counting the array told a reader that a file missing no data had a gap (0.3.3). One
+  of each is the case where the message has to say both, and no fixture produced it.
+
 ## 0.4.405
 
 - **Added** tests for `locate` at the edges of a file. `discontinuous.md` states the contract in

package/package.json

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