edfcore 0.4.387 → 0.4.389

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.389
+
+- **Added** a check that the three verifications outside `npm run check` are run by something.
+  `AGENTS.md` says CI runs all three, and that arrangement is sound and fragile: `verify:package`
+  packs the tarball and asks publint and `@arethetypeswrong/cli` what a consumer would resolve,
+  `verify:tarball` asks what npm would ship and what it must not, `verify:site` reads the generated
+  endpoints out of `website/dist`. None can run inside the suite, so the suite could not notice one
+  of them ceasing to run at all.
+- Deleting a `- run:` line from `ci.yml` is a one-line edit that turns a check into a script nobody
+  invokes, leaves every test here green, and leaves that paragraph saying CI runs it. The gap would
+  surface the next time the thing it guards broke, which is when nobody is reading CI config.
+- The set comes from `package.json` rather than from the prose — every `verify:*` script has to be
+  a step in `ci.yml`, and none of them may be reachable from `npm run check`, which is the premise
+  of the arrangement. The fenced block in `AGENTS.md` is then checked against that same set, so
+  "three" is a number this can be wrong about.
+
+## 0.4.388
+
+- **Fixed** the figure three places give for the size of this suite. The README said 1,900 or more
+  tests, the note at the foot of `installation.md` said 1,200 or more, and the docblock of
+  `browser-safety.test.ts` said 1,900-odd — three figures for one fact, the smallest of them eight
+  hundred behind. All three now say 2,000.
+- None of them was ever false, which is why nothing caught them. A claim of the form "N or more"
+  stays true forever once it is true, and the property that makes it safe is the property that
+  makes it worthless: it can never be wrong, so it is never re-read. What a reader takes from it is
+  a sense of scale, and half the real scale is a wrong impression conveyed in a true sentence.
+- **Added** the check that keeps it current: the figure has to be one figure wherever it is stated,
+  and no smaller than the number of `it(...)` and `test(...)` declarations the suite writes out. It
+  fails when the suite grows past what the pages claim, which is the direction this rots in.
+- It does not check the other direction. Four dozen of those declarations are `it.each(...)`,
+  expanding at run time to one case per row, so the count read out of the files is a floor rather
+  than the total — the right side to be wrong on, since a figure that clears it is true of the real
+  total too, but nothing here would notice one inflated past both.
+
 ## 0.4.387
 
 - **Added** a check that the published `bin` runs as a program. `cli.test.ts` and the rest drive

package/package.json

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