edfcore 0.4.429 → 0.4.431

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

package/docs/CHANGELOG.md

@@ -6,6 +6,42 @@ 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.431
+
+- **Added** tests that a 16-bit channel labelled `Status` is not a BioSemi Status channel.
+  `api-helpers.md` explains why `readTriggers` locates the channel itself rather than taking a
+  `signalIndices` — "a 24-bit EEG sample decoded as a trigger word yields plausible-looking events
+  out of ordinary data" — and that reasoning is about the wrong channel of the right file. The
+  other way in is the right channel name in the wrong kind of file.
+- `Status` is not a BioSemi word. Plenty of systems label a channel that way, and a plain EDF file
+  carrying one is an ordinary thing to be handed. Its samples are 16 bits of a measurement; a
+  BioSemi Status word is 24 bits of a latched bit field with the trigger input in the low 16 and
+  flags at bits 16, 20 and 22. Read one as the other and the low bits become codes, bit 16 becomes
+  an epoch marker that flips constantly, and what comes back is a dense list of events with real
+  timestamps from a channel that recorded a voltage. Nothing about that output says it is wrong.
+- The guard is one line, and it is what makes the documented
+  `getStatusSignal(header) !== undefined` check mean "this is an ActiveTwo recording" rather than
+  "something here is called Status". It had never been given a 16-bit file to refuse. The label
+  matching is deliberately forgiving about case and padding; the width is not.
+
+## 0.4.430
+
+- **Added** tests for a patient's date of birth being redacted out of a message that never quotes
+  the field. `redactDiagnostic` withholds identification by substituting the field's value out of
+  the message by text, and `DATE_IMPLAUSIBLE` defeats every spelling of it: the field says
+  `02-MAY-2050`, the message says `2050-05-02`, because it is comparing two dates and prints both
+  in one form. No substring of the raw field appears in that sentence. It is redacted anyway, from
+  `actual` — which carries whatever the message chose to print.
+- It is also the case with the widest reach. The other identification diagnostics fire on a
+  malformed field, so a conformant file never produces them; this one fires on a perfectly
+  conformant patient field whose only fault is a year the two-digit header rule resolved into the
+  future, which is what a recording made before 1985 or after 2084 looks like. A clinical file with
+  nothing wrong with it, printed by a command asked to withhold the patient, and a date of birth in
+  the output.
+- The other half is what must survive. Substitution is on the value, never on the code or the rule,
+  so the code, the byte offset, the field name, the spec clause and the recording's own start date
+  are all still there — and a field nobody asked to withhold is still quoted verbatim.
+
 ## 0.4.429
 
 - **Added** tests for `edfcore validate` exiting 1 because validation failed. The exit-code table on

package/package.json

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