edfcore 0.4.395 → 0.4.397

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.395";
+export declare const VERSION = "0.4.397";
 //# 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.395';
+export const VERSION = '0.4.397';
 //# 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.397
+
+- **Fixed** `website/design/og.svg`, which had been missing its final newline since it was drawn.
+  `.editorconfig` has asked for one on every file in this repository the whole time.
+- **Added** the check that would have caught it. Biome formats the `.ts`, `.mjs`, `.json` and
+  `.jsonc` files and reports a deviation as a lint error; everything else here — the markdown, the
+  two workflows, the `.astro` components, the stylesheet, the Python under `scripts/golden/`,
+  `og.svg` and `LICENSE` — was governed by `.editorconfig` and by nothing at all, and between them
+  they are most of what a reader ever opens.
+- `.editorconfig` is a request to an editor, not a check, and every way of breaking it is invisible
+  in review: a missing final newline shows as one line in one diff and then never again, and a CRLF
+  ending shows as nothing until the day a whole file appears rewritten.
+- The rules are read out of `.editorconfig` rather than restated, so deleting a line turns its
+  check off — and a separate assertion that all five are still declared is what makes that a
+  visible decision. The `[*.md]` exemption for trailing whitespace is honoured, because two spaces
+  is a hard line break.
+
+## 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

package/package.json

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