edfcore 0.4.153 → 0.4.155

package/README.md

@@ -384,7 +384,7 @@ sign and invert the clinical reading of the trace.
 the header and the validation report. Chunk joining that refuses to concatenate across a gap
 (`mergeChunks`). Timeline lookup with no read (`segmentAt`, `gapAt`, `contiguityOf`). Signal
 lookup by pattern (`matchSignals`) and ordered physical bounds (`physicalRangeOf`). See
-[API — helpers](https://edfcore.vercel.app/docs/api-helpers) and
+[API: helpers](https://edfcore.vercel.app/docs/api-helpers) and
 [CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/docs/CHANGELOG.md).
 
 **Still later, additive.** The `edffloat` logarithmic inverse transform, opt-in — still detected

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.153";
+export declare const VERSION = "0.4.155";
 //# 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.153';
+export const VERSION = '0.4.155';
 //# 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/docs/CHANGELOG.md

@@ -6,6 +6,17 @@ 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.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
+  README ships in the npm package, so it is the copy most consumers read.
+
 ## 0.4.153
 
 - **Fixed** the link on `api-validate.md` still labelled "API — helpers", after that page was

package/package.json

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

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.
  */