edfcore 0.4.503 → 0.4.505

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

package/docs/CHANGELOG.md

@@ -6,6 +6,39 @@ 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.505
+
+- **Added** the values `design-decisions.md` prints beside three of its decisions. `AGENTS.md`
+  sends every contributor to that page before proposing an architectural change, so it is the one
+  document read specifically to be argued with — and `design-absences.test.ts` checks the absences
+  it claims, not the demonstrations that justify them.
+- A decision whose example no longer produces what it prints is worse than an undocumented one: a
+  reader weighing the trade-off is reading the example to decide whether the cost is what the page
+  says it is.
+- The three chosen are each the evidence for a REJECTION rather than an illustration of an accepted
+  design — the start time as fields, which is the argument against returning a `Date`; the onset as
+  exact ticks beside its lossy seconds, which is the argument against `parseFloat`; and
+  `clampToDigitalRange` as a separate pure function, which is the argument against clamping on read
+  the way the reference implementation does.
+- The last one is asserted from both sides: the clamp produces the array the page prints, and a
+  read of the same samples does not clamp them.
+
+## 0.4.504
+
+- **Added** the values `api-primitives.md` prints beside each primitive. That page is the reference
+  for the layer under `openEdf`, and each entry ends with a line showing what comes back. Six of
+  them say something a reader would otherwise take on trust, and none was executed.
+- Two are contracts rather than examples. `again.buffer === scratch.buffer` is the whole reason
+  `decodeDigital` takes an `out` argument — zero allocations after the first, in a loop over a long
+  recording. And `decodeHeaderLatin1(bytes.subarray(0, 8))` printing `'0       '` with its padding
+  intact is the "no trimming, no interpretation" promise the paragraph above it spends five
+  sentences on: a function that trimmed would satisfy every other test of it, because almost
+  everything else compares a decoded field against its trimmed value.
+- `[ 0, 1 ]` from `findSignals` is the duplicate-label case the page annotates as something CHB-MIT
+  really does, and the reason `getSignal` has an ambiguity error at all. The sentence beside it —
+  the argument is trimmed, the match is case-sensitive, nothing else is normalised — is asserted
+  with it.
+
 ## 0.4.503
 
 - **Added** the two snippets on `api-reading.md` that print values — what `openEdf` reports for an

package/package.json

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