edfcore 0.4.370 → 0.4.372

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.370";
+export declare const VERSION = "0.4.372";
 //# 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.370';
+export const VERSION = '0.4.372';
 //# 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.372
+
+- **Added** checks for the sample-grid section of `api-helpers.md`. The page opens by naming what a
+  reader would otherwise write — `Math.round(seconds * signal.sampleRateHz)` — and tabulating three
+  ways it fails silently. Two of them are now demonstrated: an undefined rate on a zero-duration
+  file makes the expression `NaN` where the grid functions throw a `RangeError`, and rounding
+  rather than flooring reaches the next sample before its boundary.
+- The rounding rule is checked as the property the page states it as: rounding a sample's start up
+  to a whole tick keeps `gridSampleStartTicks` and `gridSampleIndexAt` inverse for every index,
+  because a truncated tick lands inside the previous sample. Verified across every sample of six
+  records at 128 samples over 0.3 s — the geometry whose boundaries are half ticks — and with the
+  truncating alternative shown to land early.
+- The third row, the index drifting by one over a long recording, is deliberately NOT asserted, and
+  the test says so. Fed the tick this package publishes, the naive expression agrees with the
+  integer arithmetic for every index of every geometry tried; the two roundings cancel. The drift
+  belongs to times a caller arrives at some other way, and a fixture manufacturing one would be
+  asserting about its own construction rather than about the library.
+
+## 0.4.371
+
+- **Added** a check on where the type tests are actually verified. `tests/types/` holds five
+  `.test-d.ts` files carrying the only assertions a runtime test cannot make — what each subpath
+  can name alone, that the documented examples typecheck, that a `Blob` and a `Response` satisfy
+  the structural shims — and vitest runs them with its own typecheck disabled.
+- That combination reports a false green. Put a plain type error into one and vitest loads it,
+  finds the runtime half fine, and prints a pass; only `npm run typecheck` catches it, because
+  `tsconfig.json` happens to include `tests`. Nothing connected that line to the five files
+  depending on it, and narrowing the include to `src` would look like an ordinary tidy-up: `npm run
+  check` would stay green, vitest would keep reporting the type tests as passing, and every
+  type-level guarantee in the package would be unchecked.
+- So the wiring is asserted rather than assumed — which config the typecheck script names, that its
+  include reaches every type test, that the only exclusion is the gitignored scratch directory, and
+  that vitest is deliberately not the thing doing the checking.
+
 ## 0.4.370
 
 - **Added** an execution of the annotations-signal section of `concepts.md`, the page the README

package/package.json

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