edfcore 0.5.13 → 0.5.15

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

package/docs/CHANGELOG.md

@@ -6,6 +6,48 @@ 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.5.15
+
+- **Added** direct tests for `floorDiv` and `ceilDiv`, which had none. `tal/ticks.ts` owns them, and
+  `ticks.test.ts` — the file named for that module — covers the onset parsers and the tick
+  conversions and neither of these. Five modules import them: `envelope.ts`, `biosemi.ts`,
+  `format-annotations.ts`, `sample-locate.ts` and `time/window.ts`. Every assertion they had was
+  incidental, made through a caller that happens to divide.
+- The whole content of both functions is the negative side. Bigint `/` truncates toward zero, so on
+  a negative numerator it is neither floor nor ceiling. Both are now checked against `Math.floor`
+  and `Math.ceil` over a grid crossing zero — 85 cells, small enough that float division is an exact
+  oracle — with `ceilDiv(a, b) === -floorDiv(-a, b)` asserted across it so the pair cannot drift
+  apart. The operator is then shown to disagree on every negative non-multiple **and only there**,
+  which is what stops the grid from proving nothing.
+- The docblock's reason for their living in `ticks.ts` — "three modules had grown their own copies
+  of the same four lines" — is enumerated out of `src/`: exactly one module declares them, five
+  call them, and each of the five imports them rather than redeclaring.
+- The last block pins the operand that makes this ordinary rather than an edge case. `trimToWindow`
+  selects sample `j` through `floorDiv((R - 1) * S, D) + 1`, and a window beginning at its own
+  chunk's start makes `R` zero — so the numerator is `-S`, negative for every file, with no unusual
+  geometry and nothing pre-stimulus about it. Truncation there returns `1` where the floor returns
+  `0`, and the window loses the first sample the caller aligned it to.
+
+## 0.5.14
+
+- **Added** the CLI's default print cap driven at all four places it is applied.
+  `cli-limit-default.test.ts` covers the NUMBER — twenty, and the four documents that promise it —
+  and its own docblock names the failure that made `DEFAULT_ITEM_LIMIT` a constant in 0.4.390: the
+  literal `20` at four separate call sites, "`header` printing twenty diagnostics while
+  `events --list` prints fifty, with both pages still saying twenty". It then exercised one of the
+  four. The three the sentence is about had never been run with the flag left off.
+- They are not reachable by accident. Each needs more than twenty of one kind of diagnostic in one
+  particular array: `header.diagnostics`, then `timeline.diagnostics` under "From the record
+  probes:" — a second application of the same local, added in 0.3.94 — and `report.diagnostics`
+  through `formatValidationReport`, which is a different formatter with its own `maxItems`. The
+  fixtures are built for it: thirty signals declaring `physicalMinimum == physicalMaximum`, thirty
+  annotation signals each carrying a malformed slot-0 TAL that both record probes see, and a
+  malformed TAL in every one of forty records.
+- Every count is compared against the cap the CLI was observed to apply rather than against a
+  literal, so this file names no number of its own and the two files move together. An explicit
+  `--limit 3` is then driven through all four as well, which is what separates a site that reads
+  `args.limit` from one that fell through to the constant.
+
 ## 0.5.13
 
 - **Added** a `NaN` budget driven through every entry point that reads one. `options.ts` exists

package/package.json

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