edfcore 0.5.36 → 0.5.38

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

package/docs/CHANGELOG.md

@@ -6,6 +6,53 @@ 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.5.38
+
+- **Added** a sweep over every `…Ticks` edfcore publishes against the `…Seconds` beside it. The
+  package's central arithmetic decision is that time is a `bigint` count of 100 ns ticks and the
+  seconds are derived from it. Twenty field pairs in `types.ts` are written that way — on the
+  header, the timeline, a segment, a gap, a location, a chunk, a chunk signal, an envelope chunk, an
+  envelope signal and an annotation — each produced by different code, and one of them was checked.
+  `timebase.test.ts` asserts "an exact tick counterpart for every second on a chunk", on chunks.
+- The other nine kinds were computed somewhere and never compared, and the failure they would
+  produce is the quiet kind: the two fields sit next to each other in an autocomplete list, a caller
+  picks whichever the surrounding code already uses, and a disagreement shows up as a plot drawn a
+  fraction of a second from where the arithmetic says it is.
+- The pairs are now enumerated out of `types.ts` and every object every entry point returns is
+  walked, over the eight `AWKWARD` shapes plus a file with a gap and a file with an overlap: 270
+  pairs, compared with `Object.is` against `ticksToSeconds`. `toBeCloseTo` would pass on a pair that
+  had drifted by exactly the thing this arithmetic exists to prevent. Every enumerated field is
+  asserted to have been reached, so none is checked in absentia, and the visited set is asserted to
+  include a negative tick count and a hundred non-zero ones.
+- `EdfAnnotation` is the pair that cannot be inferred from the names, and it is why the rule is
+  spelled out: its four onset fields are two axes, `onsetTicks` with `onsetSecondsFromHeaderStart`
+  and `onsetTicksFromFirstRecord` with `onsetSecondsFromFirstRecord`. Crossing them passes on every
+  file with no sub-second start offset, which is most of them — so the last block builds one that
+  has an offset and shows the crossed pairing failing by exactly that offset. That is the trap
+  `annotations.md` warns about, and it is what makes this pairing a rule rather than a coincidence.
+
+## 0.5.37
+
+- **Added** the safety property for the CLI. `fuzz.test.ts` states it for the library — for any byte
+  sequence, edfcore either parses it or throws an `EdfError`, never a bare `TypeError`, never a
+  hang, never believable garbage. The CLI is a second surface over the same parser, with its own
+  formatting, six commands and exit codes, and nothing had ever pointed it at bytes nobody chose.
+  Every CLI test in the suite feeds it a file written to make a point.
+- That matters because of how `cli.ts` ends. `main()` catches everything and reports
+  `edfcore: ${error.message}` with exit 1, so a `TypeError` escaping `runCli` does not crash — it
+  arrives as a line with no code, no byte offset and no `Next:` clause, wearing the prefix a real
+  diagnostic wears. The failure is indistinguishable from a working refusal unless something checks
+  the class.
+- Two properties now run over ~1,300 cases — random bytes, single-bit flips of a good file,
+  truncation at every length, and each header and per-signal field replaced with something that
+  breaks it. Every rejection is an `EdfError` whose message opens with a bracketed code and ends
+  with a `Next:` clause. And nothing reaches stdout before a rejection, so
+  `edfcore json big.edf > out.json` either writes a whole document or writes nothing — a redirect
+  cannot leave a half-written file beside a non-zero exit.
+- The exit codes are checked for reachability rather than assumed: 0 for a clean file, 1 for one
+  that reads and fails validation, 2 for bad usage. `parseArgs` over 500 arbitrary argv arrays
+  throws nothing but `CliUsageError`, which is what keeps 2 distinguishable from 1.
+
 ## 0.5.36
 
 - **Added** the `ByteSource` `data-sources.md` tells you to write, written and read through. "Writing

package/package.json

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