edfcore 0.6.36 → 0.6.37

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

package/docs/CHANGELOG.md

@@ -6,6 +6,26 @@ 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.37
+
+- **Fixed** an incomplete sentence on `api-reading.md`. It said the index traversal "is chunked so
+  memory stays bounded whatever the file size: each chunk holds
+  `min(4 MiB, maxMaterializeBytes) / recordByteLength` records, and never fewer than one" — which
+  is true and reads as though a small budget only makes the scan slower. Below one record's worth
+  it does not: one record cannot be read within the budget and there is no smaller count to ask
+  for, so the scan is refused. The page says that now, and says the refusal names the record's size.
+- **Added** `the-page-says-always.test.ts`, which executes the five claims on that page that say
+  "always", "never" or "every" against all seventeen shapes. Each was written when the matrix held
+  eight, and a universal claim is only as checked as the widest file anyone pointed it at — 0.6.36
+  is what happens when one meets a shape it had not: four sweeps turned out to be asserting
+  something narrower than they said. The claims are read off the page, so a rewording fails here.
+- Two are worth naming. `readAnnotations` answers on a file with NO annotations channel, returning
+  one onset per record from the nominal grid — "always" includes the file with nowhere to store an
+  annotation. And on that same file a budget of one byte does not refuse, because the page's next
+  sentence says such a file "is not scanned at all, because its record onsets are arithmetic": the
+  two claims agree, and the test checks that they do rather than exempting one.
+- No library change.
+
 ## 0.6.36
 
 - **Added** a seventeenth shape to the `AWKWARD` matrix: records that overlap in time, where a

package/package.json

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