edfcore 0.4.295 → 0.4.297

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.295";
+export declare const VERSION = "0.4.297";
 //# 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.295';
+export const VERSION = '0.4.297';
 //# 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.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
+  documented script is real; nothing checked the other direction, and `format`, `release` and the
+  three `verify:*` scripts had accumulated unmentioned. A contributor-facing script nobody
+  documents is a script nobody runs — `verify:tarball` and `verify:site` were both added this week
+  and would have been found only by reading `package.json`.
+- The three `verify:*` get their own block with the reason they are not in `npm run check`: each
+  needs the network or an artifact `check` does not build, and `check` staying offline is a
+  property `tests/README.md` opens with.
+
 ## 0.4.295
 
 - **Corrected** the release script's closing message, which 0.4.294 made false one release ago. It

package/package.json

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