edfcore 0.4.390 → 0.4.392

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.392
+
+- **Added** a check that the docblocks reach the published types, which five other checks quietly
+  assume. `config/tsconfig.build.json` sets `removeComments: false`, and that one line is why the
+  module docblock of `src/index.ts` is the hover text an editor shows over an import, and why
+  `readme-status.test.ts`, `node-floor.test.ts`, `module-layers.test.ts`, `file-references.test.ts`
+  and `next-clause.test.ts` each say some version of "this comment ships, so a stale one is stale
+  in the package".
+- Nothing asserted it. Flip the flag and all five keep passing — they read `src/`, and the claim
+  they draw from it is about `dist/`. What changes is that the published `.d.ts` files lose every
+  line of documentation, an editor shows a bare signature on hover, and the package's reasoning
+  about itself stops being visible to anyone who installs it.
+- The setting is asserted and then the artifact is checked rather than the setting: a distinctive
+  sentence from three source docblocks has to be present, verbatim, in the `.d.ts` built from it.
+  `removeComments` is one of several ways to lose them, and reading the file catches the rest.
+
+## 0.4.391
+
+- **Added** a check that the defaults the option tables print are the defaults the code applies.
+  Four reference pages carry a `Default` column, and between them they publish the numbers almost
+  every caller gets by passing nothing: 256 MiB for `maxMaterializeBytes`, 1 MiB blocks and a
+  64 MiB budget for `cachedSource`, four in-flight requests for `httpSource`.
+- They are observed rather than imported. Comparing the tables with `DEFAULT_MAX_MATERIALIZE_BYTES`
+  would pass just as happily on a release where that constant is no longer what resolves — the
+  failure `options.ts` opens by describing, where the budget is resolved in six modules across the
+  stack. So the budget is read off the `EdfBudgetError` a refused allocation carries, the block
+  size off the read the cache issues, the LRU budget off the clamp it applies to an oversized
+  block, and the concurrency off the peak number of requests in flight.
+- Finding out what 256 MiB is costs a few hundred bytes: the budget is checked against the header
+  geometry before anything is allocated, so the fixture is a header that declares 4,000 records of
+  120,000 bytes over a source that fabricates them.
+- The last check is the closure. Every numeric cell in those `Default` columns has to be one of the
+  values observed here, so a newly documented number either gets an observation or fails and names
+  the page it is on.
+
 ## 0.4.390
 
 - **Changed** the CLI's print cap from a literal repeated at four call sites to one

package/package.json

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