edfcore 0.4.449 → 0.4.451

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

package/docs/CHANGELOG.md

@@ -6,6 +6,44 @@ 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.451
+
+- **Added** a property test for `bucketCount` over arbitrary windows. `api-helpers.md` calls it
+  "the field to read before indexing, and it is not always the `buckets` you asked for" — a caller
+  who sizes a canvas to 800 pixels, asks for 800 buckets and loops to 800 reads past the end of
+  `counts` on any run shorter than 800 samples, which is every run near the end of a recording and
+  every run between two gaps.
+- The two calls answer differently and both answers are deliberate. `readEnvelope` clamps to the
+  densest signal's sample count, because a grid with more buckets than samples has columns that
+  mean nothing. `readEnvelopeAtResolution` does not, because its contract is the bucket WIDTH:
+  shortening the count would shorten the grid rather than coarsen it, and a time axis asked for
+  30 s per bucket has to keep getting it.
+- Both rules are exactly the kind that hold for the case someone checked — a run long enough for
+  the clamp never to bite, a resolution dividing the span exactly — so they are now checked over
+  generated geometries, along with the invariant a caller actually indexes on: every signal's
+  `counts`, `min` and `max` are `bucketCount` long, whatever the count turns out to be.
+
+## 0.4.450
+
+- **Added** a property test that `printable` never changes the width of what it is given. Every
+  table the package prints depends on it: `formatHeader` pads a label into a column, the CLI's
+  `signals` output is tab-separated for `cut -f2`, and the validation report lines observed ranges
+  up under a heading — all on text read out of a file, where EDF says a label is sixteen bytes and
+  says nothing about what may be in them.
+- The module's docblock states the rule and rejects two alternatives, both of which are the natural
+  thing to reach for and both correct-looking: a stripped control character is gone, an escaped one
+  is legible. Either shifts a column by a character per occurrence. Those alternatives are now an
+  executable contrast rather than a comment — the property computes both and shows one shortens and
+  one lengthens.
+- The generated text covers what a fixture-writer does not think of: astral characters, which are
+  two UTF-16 units and one iteration of a `for…of`; lone surrogates, which are one of each; the
+  Latin-1 supplement, which a European electrode label really contains; and the line separator the
+  docblock argues should pass through. DEL is drawn separately, because a generator covering only
+  0x00-0x1f leaves the second half of the condition untouched while looking thorough.
+- Three invariants, and the third is what makes the first two mean anything: the length is
+  unchanged, no C0 or DEL survives, and every character that was not one is exactly what it was.
+  Without the third, returning a string of dots would satisfy the other two.
+
 ## 0.4.449
 
 - **Added** a check that the sourcemaps in the published package point at files the package ships.

package/package.json

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