edfcore 0.4.154 → 0.4.156

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

package/dist/record-index.d.ts

@@ -20,8 +20,8 @@
  * - `buildRecordIndex()` is the only function here that touches every record, it is chunked so
  *   memory stays bounded whatever the file size, and it is never called implicitly.
  *
- * A probe reads a whole data record rather than just the annotation signal's region. That is
- * decision 7 of the design — the unit of I/O is the record range, never the channel range — and
+ * A probe reads a whole data record rather than just the annotation signal's region. That is the
+ * design's "unit of I/O" decision — the unit is the record range, never the channel range — and
  * it is also what lets `decodeAnnotations` own the timekeeping rule: it requires the record's
  * full bytes, and reading less would mean reimplementing that rule here.
  */

package/dist/record-index.js

@@ -20,8 +20,8 @@
  * - `buildRecordIndex()` is the only function here that touches every record, it is chunked so
  *   memory stays bounded whatever the file size, and it is never called implicitly.
  *
- * A probe reads a whole data record rather than just the annotation signal's region. That is
- * decision 7 of the design — the unit of I/O is the record range, never the channel range — and
+ * A probe reads a whole data record rather than just the annotation signal's region. That is the
+ * design's "unit of I/O" decision — the unit is the record range, never the channel range — and
  * it is also what lets `decodeAnnotations` own the timekeeping rule: it requires the record's
  * full bytes, and reading less would mean reimplementing that rule here.
  */

package/dist/types.d.ts

@@ -430,7 +430,7 @@ export interface EdfRecordIndex {
      * One read of that WHOLE data record — `header.recordByteLength` bytes. Memoised.
      *
      * Not the annotation region alone, which this said until 0.3.71. The unit of I/O in edfcore is
-     * the record, never the channel (decision 7), and `decodeAnnotations` owns the timekeeping rule
+     * the record, never the channel, and `decodeAnnotations` owns the timekeeping rule
      * and needs the record's full bytes to apply it. On a 64-channel file the region is 32 bytes of
      * a 16,416-byte record, so "targeted" understated the read by 513x — and `locate()` issues
      * O(log recordCount) of them, which is exactly the number a caller planning HTTP range requests

package/docs/CHANGELOG.md

@@ -6,6 +6,18 @@ 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.156
+
+- **Removed** the other "(decision 7)" citation, in `types.ts`. Same retired numbering, and this one
+  ships in `dist/types.d.ts` as the hover text for `EdfRecordIndex.onsetTicks`. The sentence already
+  states the decision, so the reference added nothing a reader could follow.
+
+## 0.4.155
+
+- **Fixed** a docblock citing "decision 7 of the design". The numbered DESIGN.md it referred to no
+  longer exists; the decision record is the design-decisions page, whose sections are named rather
+  than numbered. It now cites the decision by name.
+
 ## 0.4.154
 
 - **Fixed** the README link still labelled "API — helpers", the last site of that rename. The

package/package.json

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

package/src/record-index.ts

@@ -20,8 +20,8 @@
  * - `buildRecordIndex()` is the only function here that touches every record, it is chunked so
  *   memory stays bounded whatever the file size, and it is never called implicitly.
  *
- * A probe reads a whole data record rather than just the annotation signal's region. That is
- * decision 7 of the design — the unit of I/O is the record range, never the channel range — and
+ * A probe reads a whole data record rather than just the annotation signal's region. That is the
+ * design's "unit of I/O" decision — the unit is the record range, never the channel range — and
  * it is also what lets `decodeAnnotations` own the timekeeping rule: it requires the record's
  * full bytes, and reading less would mean reimplementing that rule here.
  */

package/src/types.ts

@@ -482,7 +482,7 @@ export interface EdfRecordIndex {
    * One read of that WHOLE data record — `header.recordByteLength` bytes. Memoised.
    *
    * Not the annotation region alone, which this said until 0.3.71. The unit of I/O in edfcore is
-   * the record, never the channel (decision 7), and `decodeAnnotations` owns the timekeeping rule
+   * the record, never the channel, and `decodeAnnotations` owns the timekeeping rule
    * and needs the record's full bytes to apply it. On a 64-channel file the region is 32 bytes of
    * a 16,416-byte record, so "targeted" understated the read by 513x — and `locate()` issues
    * O(log recordCount) of them, which is exactly the number a caller planning HTTP range requests