edfcore 0.4.323 → 0.4.325

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

package/docs/CHANGELOG.md

@@ -6,6 +6,33 @@ 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.325
+
+- **Added** a check for the claim `edf-format.md` closes with: "Every diagnostic edfcore emits
+  names the clause it comes from." That is the promise that makes a warning adjudicable — `EDF+
+  additional specification 5` can be checked against a document — and nothing held it.
+  `specReference` is optional on `DiagnosticInit`, so leaving it out is neither a type error nor a
+  lint error, and most emission sites pass it positionally through a helper, which is why a static
+  scan of the object literals answers the wrong question.
+- So the diagnostics are asked instead: nine targeted files for the header defects that need a
+  particular pair of fields, plus a bit-flip sweep over the first 900 bytes of a well-formed EDF+
+  file. Between them they produce twenty-four of the forty-six codes, every one of which names a
+  document rather than a feeling. The reach is asserted rather than assumed, and the docblock says
+  plainly that this demonstrates the claim over half the table rather than proving it over all of
+  it — the other twenty-two need conditions one fixture cannot reach.
+
+## 0.4.324
+
+- **Added** an execution of the TAL grammar `edf-format.md` prints as ABNF. Two of its five lines
+  carry a rule the rest of the page argues from: `Onset` requires its sign and `Duration` forbids
+  one, and `tal/ticks.ts` refuses a signed duration outright because a signed duration means the
+  field layout is not the one being read. Both are now checked against the page's own text.
+- The claim underneath the block is proved rather than quoted. "Every byte of a multi-byte UTF-8
+  sequence is at least `0x80` and can never collide with one of them" is why the region may be
+  split on the structural bytes BEFORE decoding, and it is checked over every code point above
+  U+007F rather than sampled — about three million bytes. The other order, which the page says
+  corrupts any non-ASCII annotation, is exercised end to end through a file carrying one.
+
 ## 0.4.323
 
 - **Added** an execution of the four-line record arithmetic on `edf-format.md` — the sample width

package/package.json

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