edfcore 0.4.476 → 0.4.478

package/README.md

@@ -1,6 +1,5 @@
 # edfcore
 
-[![exports](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fedfcore.vercel.app%2Fapi.json&query=%24.exports.total&label=exports&color=blue)](https://edfcore.vercel.app/api.json)
 [![downloads](https://img.shields.io/npm/dt/edfcore?label=downloads)](https://www.npmjs.com/package/edfcore)
 
 edfcore reads EDF, EDF+, BDF and BDF+ biosignal files in TypeScript, in the browser and in
@@ -310,10 +309,10 @@ 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
-`exports` badge at the top reads [`/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 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.
 
 ---
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,38 @@ 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.478
+
+- **Removed** the `exports` badge from the top of the README, at the user's request. The number it
+  showed is still in the API surface table further down, and still counted rather than typed.
+- `/api.json` stays. The README links it, the site serves it, and the reason it exists — a
+  published count that a human wrote is the site footer that read "Version 0.1.0" through three
+  minor series — is unchanged by the badge going. Its docblock said it existed to back the badge,
+  which is no longer true, so it now says what it is.
+- The badge-contract test was entirely about that badge: it pulled the JSONPath out of the
+  shields.io URL and walked it through the object the endpoint builds, because shields.io renders
+  a broken path as "invalid" in a corner nobody reads. With no badge there is no URL to read, so
+  the file has been retired to the repository's `deleted/` folder — and the half of it that still
+  has a subject, that `exports.total` resolves and equals the README's table, moved into
+  `api-badge.test.ts` rather than leaving with it.
+- That file now also asserts the badge is absent, so it cannot drift back in beside a table that
+  states the same number one line below it.
+
+## 0.4.477
+
+- **Added** the case where a 206 says which bytes it sent and not how large the resource is. The
+  short-tail message has a clause for that — "the end of the resource" rather than "the end of a
+  N-byte resource" — and nothing had ever taken it, because every case supplied a readable total.
+- A streaming origin produces it as a matter of course: the length is not known when the response
+  heads out, so RFC 7233's `*` goes in the slot and the range is still exact. Both spellings are
+  covered, the star and a total that is simply unreadable, because the clause is about
+  readability rather than about the star.
+- What it must not do is print the number it does not have. "the end of a undefined-byte
+  resource" is the shape that mistake takes, and it lands in the one sentence a reader consults
+  to decide whether their `options.byteLength` or their CDN is at fault. The assertions rule out
+  both `-byte resource` and the word `undefined`, and keep the number that IS known — the 32 the
+  source was built for, which is what the message is telling them to go and check.
+
 ## 0.4.476
 
 - **Added** the zero-record-duration case to `readTriggers`, the last reader in the package

package/package.json

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