edfcore 0.4.297 → 0.4.299

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

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.299
+
+- **Extended** `verify:site` to check the generated markdown carries the page, not just its head.
+  Every check before this one asked whether a URL exists, and a generator that emitted the
+  frontmatter and dropped `entry.body` would have satisfied all of them: `llms-full.txt` would
+  still list all 23 pages, every `.md` twin would still render its title and canonical link, and
+  the whole thing would be a table of contents for text nobody shipped. `entry.body` is one
+  property access away from being forgotten in either generator.
+- One distinctive prose line is taken from the middle of each page's source and looked for in both
+  outputs. Dropping it from the twin route flagged all 23.
+
+## 0.4.298
+
+- **Corrected** the promise over the "things that look like bugs and are not" list, which 0.4.254
+  made untrue. It says "each has a test pinning it and a comment explaining why", and that held for
+  the seven code rules — the scaling expression, the `TextDecoder` ban, `readWindow` returning an
+  array, `scale` being `undefined`, no `Date`, no bitwise on an offset, `info` under `strict` — and
+  then an eighth entry was added about the `archive/pre-squash-2026-08-16` branch being
+  load-bearing. That one is a fact about the repository rather than about the code, and an offline
+  suite has no way to check a branch on a remote. An unqualified "each" over a list where one has
+  no test is the shape this project keeps correcting elsewhere.
+
 ## 0.4.297
 
 - **Exercised** the inspector's sample recording, which nothing had. `sample-edf.ts` writes an

package/package.json

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