edfcore 0.5.12 → 0.5.14

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.12";
+export declare const VERSION = "0.5.14";
 //# 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.12';
+export const VERSION = '0.5.14';
 //# 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.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
+  because `maxMaterializeBytes` is typed `number`, which admits `NaN`, and `NaN` arrives without
+  anyone writing it — `Number(process.env.EDF_BUDGET)`, an absent query parameter, a missing JSON
+  key. Its docblock states the reach the guard needs: the option is resolved in six modules and read
+  raw and handed on in two more, and "a guard that only one of the eight applies is not a guard".
+- Nothing checked the eight. `options.test.ts` checks the resolver in isolation, and
+  `budget-boundary.test.ts` enumerates the five sites that compare a REQUIREMENT against the budget
+  — a different set, reached only by a request large enough to refuse. A `NaN` is refused earlier
+  than that, by the resolver, in modules that list names: `record-index.ts` compares nothing, and
+  `biosemi.ts` resolves nothing.
+- The eight are now read out of `src/` and split by what they do with the option, with the counts
+  checked against the sentence in the docblock that states them. Each is then driven through its own
+  public entry point — `readRecordBytes`, `readRecords`, `decodeDigital`, `toPhysical`,
+  `readEnvelope`, `buildRecordIndex`, `validateRecording` on both its branches, and `readTriggers`,
+  which owns no resolver and borrows the scan chunker's.
+- The eighth is stated rather than asserted away: `cachedSource` hands the option to the source it
+  wraps, so a `NaN` survives it and is refused by the first resolving module downstream. That is the
+  design — a cache is not the layer that owns a materialisation budget — and it is now a fact the
+  suite records instead of a gap in it.
+
 ## 0.5.12
 
 - **Added** the six mistakes `AGENTS.md` tells a code generator to avoid, run. That file carries two

package/package.json

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