edfcore 0.4.475 → 0.4.477

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

package/docs/CHANGELOG.md

@@ -6,6 +6,37 @@ 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.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
+  without one. `formatHeader`, `resolveTimeWindow`, `trimToWindow`, `gridSampleStartTicks` and
+  `readEnvelope` all have theirs; BDF permits a zero record duration, and this is the reader whose
+  own comment states what it means — every sample of every record sits at one instant.
+- What that costs is that time can no longer order the events, and `sampleIndex` is the only thing
+  that can. Three trigger runs come back as three events, all at tick 0, at sample indices 0, 2
+  and 5 — so the change detection still works when the times are all equal, which is the part
+  nothing else in the suite says.
+- The all-or-nothing rule is pinned with it: a window starting after that instant yields nothing
+  rather than the tail of the recording, and a zero-length window yields nothing either.
+- The guard the comment sits on is NOT claimed to be covered by this, and the test says so.
+  `ceilDiv(s * 0n, samplesPerRecord)` is 0 for every `s`, so its two branches agree on every
+  input and no test can tell them apart. What is checked is the outcome.
+
 ## 0.4.475
 
 - **Added** the boundary cases for `quote`, which is what keeps a `raw:` line on one line however

package/package.json

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