edfcore 0.6.34 → 0.6.36

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

package/docs/CHANGELOG.md

@@ -6,6 +6,53 @@ 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.6.36
+
+- **Added** a seventeenth shape to the `AWKWARD` matrix: records that overlap in time, where a
+  record starts before the one before it ended and two records claim the same instant. edfcore has
+  always known about them — the gap list carries one with a negative duration (0.2.69),
+  `mergeChunks` refuses the join, `edfcore gaps` prints it in its own column, and the probe raises
+  `RECORD_ONSET_SPACING_VIOLATION`, a warning rather than an error because an overlapping file is
+  still readable.
+- **Fixed** four sweeps that were asserting things true only of files whose records do not overlap,
+  which nothing had ever supplied:
+  - `header-helpers-agree` said the sum of the record durations never exceeds the span. It exceeds
+    it by exactly the overlap, because an overlap counts an instant twice.
+  - `timeline-helpers-agree` said an instant inside a segment is answered with THAT segment, and
+    that a gap's midpoint is in no segment. Two segments contain an overlapped instant, and an
+    overlap's interval runs backwards, so its midpoint is inside a segment rather than in a hole.
+  - `reading-helpers-agree` said a window at a sample's start begins at that sample's record, and
+    that a window's chunks join. Neither holds here — and the second was the half of its own
+    comment the code had never run: "either join or are refused with a reason" had only ever seen
+    joining.
+- None of the four was a defect in `src/`. The library refuses the unindexed read with a message in
+  the file's own numbers ("records covering 6 s are packed into a 3.5 s span"), returns both
+  covering records in separate chunks once it has an index, and refuses to concatenate them. Each
+  sweep now states the weaker thing true of every file and the stronger thing true of this one,
+  rather than exempting the shape.
+- That is what a matrix is for: the claims were not wrong because anyone was careless, they were
+  claims with no counterexample.
+
+## 0.6.35
+
+- **Added** the census that closes the class four releases in a row have been fixing. A sample rate
+  of `68.96551724137932` in a nine-character column (0.6.23), a signal index of 1000 in three
+  (0.6.24), a negative or hundred-hour clock in twelve (0.6.25), an observed range and sample count
+  that were not padded at all (0.6.34) — the same mistake in four formatters, each found by looking
+  at output rather than by anything failing.
+- `every-column-knows-its-width.test.ts` lists every `padStart` and `padEnd` in `src/` that lays
+  out a column, with one of three reasons its width is safe: MEASURED from the rows being printed,
+  bounded by the FILE FORMAT (a label is 16 bytes, `kind` is one of two words, a rate is rounded to
+  fit), or bounded by an ARGUMENT no test can build.
+- Two are in that last group and are named rather than assumed: the per-code diagnostic count and
+  the event count, with the arithmetic written out — seven digits is 9,999,999 of one code, and the
+  record count field is eight characters, so a per-record code on the largest file the format can
+  describe would need eight. They are not measured because no test can construct the report that
+  would show it, and saying so is better than a floor nobody can justify.
+- A new width fails until it says which of the three it is. Zero-padding is excluded by pattern: a
+  clock digit spelling itself is not a place in a table.
+- No behaviour changed.
+
 ## 0.6.34
 
 - **Fixed** the observed-ranges block in `edfcore validate` falling where the numbers left it. The

package/package.json

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