edfcore 0.4.362 → 0.4.363

package/README.md

@@ -151,8 +151,12 @@ for (const d of recording.header.diagnostics) {
 }
 ```
 
-Every diagnostic carries the field, the byte offset, the raw bytes as written, the spec clause it
-violates, and what to do next. Pass `{ strict: true }` and the first one throws instead.
+Every diagnostic names the field at fault, the spec clause it violates, and what to do next. One
+anchored to a header field carries that field's byte offset and its raw bytes as written too. The
+two about the spacing of record onsets carry neither, because the defect is a relationship between
+records rather than a value sitting at an offset — they name the record instead where one record is
+at fault, and the whole file where the shape is. Pass `{ strict: true }` and the first one throws
+instead.
 
 **Digital and physical are two functions.** `chunk.signals[i].digital` is an `Int32Array` of
 the values as stored. `toPhysical(signal, digital)` returns a `Float64Array` in the signal's own

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

package/docs/CHANGELOG.md

@@ -6,6 +6,23 @@ 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.363
+
+- **Corrected** the README's promise about diagnostics and widened 0.4.325's check to cover it. It
+  said every diagnostic carries "the field, the byte offset, the raw bytes as written, the spec
+  clause it violates, and what to do next". Two of them carry neither the offset nor the raw bytes:
+  `DISCONTINUITY_IN_CONTINUOUS_FILE` and `RECORD_ONSET_SPACING_VIOLATION` are about the spacing of
+  record onsets, so there is no one offset the defect sits at and no field text to quote.
+- That is the right answer rather than a gap — an offset invented for them would point at a record
+  that is individually fine — so the sentence now says which diagnostics carry which. It also
+  distinguishes the two ways the first of them is raised: against the last probed record when one
+  record is at fault, and as a whole-file summary when the shape is, which is why not even a record
+  index is always available.
+- The sweep now checks all five properties instead of the spec clause alone: every diagnostic names
+  its field and says what to do next, everything anchored to a header field carries an offset and
+  its raw bytes, and the two relational codes carry neither and are asserted to be reached, so the
+  exemption is examined rather than assumed.
+
 ## 0.4.362
 
 - **Added** a check over the edfcore column of the capabilities table on `comparison.md`. Seven

package/package.json

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