edfcore 0.4.382 → 0.4.384

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.382";
+export declare const VERSION = "0.4.384";
 //# 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.382';
+export const VERSION = '0.4.384';
 //# 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.384
+
+- **Added** the browser half of `node-floor.test.ts`. The Node floor is checked in eleven places
+  against `engines.node`, a field a package manager reads; the browser floor has no such field —
+  no browserslist, nothing in `package.json` — and its three statements (the README's compatibility
+  line, the Runtimes table on `installation.md`, and the summary string `llms.txt` hands an agent)
+  were three independent sentences that happened to agree.
+- The table is the source, since it is the one with the reasoning printed under it, and the other
+  two are checked against it. A floor raised in one place tells a reader their browser is supported
+  on one page and unsupported on the next.
+- The check with teeth is the last one. The table's stated basis is "ES2022 syntax, `BigInt`,
+  `Blob.prototype.slice`, and `TextDecoder`", and the first of those is not an observation about
+  the code — it is `target` and `lib` in `config/tsconfig.build.json`. Raising either to ES2023 is
+  a one-word edit that compiles, ships, passes every other test here, and invalidates all three
+  published floors at once.
+- It does not check that 94, 93 and 15.4 are the right versions for those four features. That is a
+  question about browser release history, which nothing in this repository can settle.
+
+## 0.4.383
+
+- **Added** a check for the last paragraph of `data-sources.md`, which says what survives
+  `close()`: the header and the timeline stay readable, and `readRecords`, `readWindow`,
+  `readAnnotations` and an unmemoised `index.locate` fail. Every `fileSource` example on the site
+  is wrapped in `try { … } finally { await source.close?.() }`, so a recording outliving its handle
+  is the ordinary shape of a program here, and that paragraph was the only statement of which half
+  of the object still works.
+- The carve-out in it turned out to be narrower than it reads. A probed index memoises records 0
+  and n−1 at open and every record a search walks over, so `locate(0.5)` answers after the close
+  only if it already ran before it — on a freshly opened file the binary search probes a midpoint
+  first. Both cases are pinned, since a later memoisation change makes that quietly more generous.
+- It does not claim the rejection is an `EdfError`. It is whatever the source raises: for
+  `fileHandleSource` that is Node's own `Error: file closed`, and `isEdfError` returns false for
+  it. Closing your own handle is not a file defect.
+
 ## 0.4.382
 
 - **Fixed** the docblock at the top of `scripts/release.mjs`, which described the scheme that was

package/package.json

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