edfcore 0.4.391 → 0.4.393

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.391";
+export declare const VERSION = "0.4.393";
 //# 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.391';
+export const VERSION = '0.4.393';
 //# 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.393
+
+- **Added** a property test for the rule `design-decisions.md` states about out-of-range samples: a
+  sample outside the declared digital range comes back as it was stored, is counted for free during
+  decode, and converts on the affine map that produced the samples inside the range. Clamping
+  instead flat-tops real peaks and draws saturation the hardware did not produce, so `edfcore` ships
+  the clamp as a separate function you call on purpose — EDFlib clamps on read, and cross-validating
+  against it needs the same operation.
+- The unit tests check that with chosen values against chosen ranges. What examples cannot say is
+  that nothing clamps for some combination: a negative gain, a range that does not straddle zero, a
+  24-bit signal whose declared span is narrower than a 16-bit one's. Those are the shapes where a
+  stray `Math.min` looks correct in review.
+- Four properties over generated ranges, generated samples and both storage widths: the decoded
+  integers are the integers written, `outOfDigitalRangeCount` is what an independent pass finds,
+  the physical step per digital unit outside the range equals the step inside it — which is what
+  "extrapolates" means — and `clampToDigitalRange` moves exactly the samples outside the range and
+  nothing else.
+
+## 0.4.392
+
+- **Added** a check that the docblocks reach the published types, which five other checks quietly
+  assume. `config/tsconfig.build.json` sets `removeComments: false`, and that one line is why the
+  module docblock of `src/index.ts` is the hover text an editor shows over an import, and why
+  `readme-status.test.ts`, `node-floor.test.ts`, `module-layers.test.ts`, `file-references.test.ts`
+  and `next-clause.test.ts` each say some version of "this comment ships, so a stale one is stale
+  in the package".
+- Nothing asserted it. Flip the flag and all five keep passing — they read `src/`, and the claim
+  they draw from it is about `dist/`. What changes is that the published `.d.ts` files lose every
+  line of documentation, an editor shows a bare signature on hover, and the package's reasoning
+  about itself stops being visible to anyone who installs it.
+- The setting is asserted and then the artifact is checked rather than the setting: a distinctive
+  sentence from three source docblocks has to be present, verbatim, in the `.d.ts` built from it.
+  `removeComments` is one of several ways to lose them, and reading the file catches the rest.
+
 ## 0.4.391
 
 - **Added** a check that the defaults the option tables print are the defaults the code applies.

package/package.json

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