edfcore 0.4.394 → 0.4.396

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.394";
+export declare const VERSION = "0.4.396";
 //# 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.394';
+export const VERSION = '0.4.396';
 //# 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.396
+
+- **Added** a check that the share card is the image the page says it is. `og.png` is 537 KB of
+  pixels nothing in this repository opens, and it is the only thing many people ever see of the
+  project — every link posted in a channel or pasted into a chat renders it.
+- `Base.astro` declares `og:image:width` and `og:image:height` to scrapers that lay the preview out
+  before the bytes arrive, so wrong numbers letterbox or crop the card at the far end, where nobody
+  who could fix it is looking. Those are now read out of the PNG's own IHDR chunk rather than taken
+  on trust.
+- The export is `qlmanage` then `sips -c 630 1200`, which keeps the middle of a square thumbnail.
+  That works only because `og.svg` is a 1200x1200 canvas with the card in a band offset by half the
+  leftover; changing the canvas takes the wrong rows, quietly, because a wrongly cropped card is
+  still a card. The offset is now derived from the two numbers instead of being a literal.
+- `og:image:alt` is what a screen reader says and what shows when the image fails. It quotes the
+  line the card prints, names the annotation the card draws and calls the trace green, and all
+  three are now checked against the SVG.
+
+## 0.4.395
+
+- **Added** a check that `vercel.json` describes the site this repository builds. It is the one
+  configuration file here nothing reads on a normal day — the tests do not need it, `npm run check`
+  does not touch it, and it takes effect on a machine nobody watches — and its couplings are all
+  silent when broken.
+- The build command names four scripts across two workspaces, and each has to exist. Its
+  `outputDirectory` has to be the directory `check-site-output.mjs` inspects, or one of them is
+  looking at a build nobody serves. The two `Content-Type: text/plain` rules have to name routes a
+  page generator produces, or `/llms.txt` arrives as a download while CI still finds the file in
+  `dist/` and passes. And `trailingSlash` is stated here and again in `astro.config.mjs` in
+  different vocabularies: disagreeing gives every documentation URL a redirect it did not ask for.
+- The `Permissions-Policy` row is checked for a different reason. `inspector-privacy.test.ts`
+  proves the demo sends nothing; this is the other half — the header that stops the page asking for
+  a camera, a microphone or a location at all. That is the kind of line dropped in a config tidy-up
+  because nothing appears to use it.
+
 ## 0.4.394
 
 - **Added** a check that every field the error tables on `api-errors.md` document is on the error

package/package.json

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