edfcore 0.6.68 → 0.6.69

package/README.md

@@ -321,10 +321,13 @@ the reason to trust the reader.
 
 Every number above is asserted against the package by
 [`tests/integration/api-surface.test.ts`](tests/integration/api-surface.test.ts) — it counts the
-real exports, renders the real `--help`, and fails when this table drifts from either. The same
-counts are served at [`/api.json`](https://edfcore.vercel.app/api.json), which the documentation
-site generates at deploy time by importing the three published entry points and counting them, so
-it needs no maintenance at all.
+real exports, renders the real `--help`, and fails when this table drifts from either.
+
+The first two rows are also served at [`/api.json`](https://edfcore.vercel.app/api.json), which
+the documentation site generates at deploy time by importing the three published entry points and
+counting what they export, so it needs no maintenance at all. The other three are not there and
+cannot be: types are erased before that endpoint can see them, and the diagnostic codes and CLI
+commands are counted by reading source rather than by importing a barrel.
 
 ---
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,20 @@ 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.69
+
+- **Fixed** the README saying that the API-surface table's counts "are served at `/api.json`".
+  Two of the five rows are. The endpoint serves the entry-point count and the total number of
+  runtime exports, and cannot serve the other three: its own docblock says "Runtime exports only.
+  Types are erased before this file can see them", and the diagnostic codes and CLI commands are
+  the same problem — `api-surface.test.ts` counts those by reading source, which is not something
+  a build-time endpoint importing `dist` can do.
+- A reader who took "the same counts" at its word went looking for a machine-readable public-type
+  count and found a document that does not mention types.
+- The test reads the endpoint rather than importing it: it names `edfcore` by package, which
+  resolves through `website/node_modules`, and reaching into that directory is what broke CI on
+  0.4.231 through 0.4.236.
+
 ## 0.6.68
 
 - **Fixed** every docs page describing itself two ways at once. `og:type` said `website` while the

package/package.json

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