edfcore 0.4.296 → 0.4.298

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

package/docs/CHANGELOG.md

@@ -6,6 +6,29 @@ 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.298
+
+- **Corrected** the promise over the "things that look like bugs and are not" list, which 0.4.254
+  made untrue. It says "each has a test pinning it and a comment explaining why", and that held for
+  the seven code rules — the scaling expression, the `TextDecoder` ban, `readWindow` returning an
+  array, `scale` being `undefined`, no `Date`, no bitwise on an offset, `info` under `strict` — and
+  then an eighth entry was added about the `archive/pre-squash-2026-08-16` branch being
+  load-bearing. That one is a fact about the repository rather than about the code, and an offline
+  suite has no way to check a branch on a remote. An unqualified "each" over a list where one has
+  no test is the shape this project keeps correcting elsewhere.
+
+## 0.4.297
+
+- **Exercised** the inspector's sample recording, which nothing had. `sample-edf.ts` writes an
+  EDF+C file in the browser so the demo has something to decode without asking a visitor for a
+  patient recording — three hundred lines of EDF writing that the test suite cannot reach, because
+  anything imported from `website/` drags in a tsconfig the root install does not have. `verify:site`
+  runs in the job that installed the site's dependencies, so it can.
+- A round trip rather than a snapshot: the generator is a writer, edfcore is a reader, and the
+  page's headline numbers are what the reader has to find — EDF+C, five signals, 120 seconds, and
+  no error-severity diagnostic. If those agree, both agree about the format. Verified by deleting a
+  channel and watching it report four.
+
 ## 0.4.296
 
 - **Documented** the commands that existed and no page mentioned. 0.4.268 checks that every

package/package.json

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