edfcore 0.6.80 → 0.6.82

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.6.82
+
+- **Fixed** the clock the inspector prints beside each event, which read
+  `onsetSecondsFromFirstRecord` and floored it. `format-annotations.ts` states the rule for the
+  library's own event list and why it is not fussiness: the seconds are "a float64 produced by
+  dividing an exact tick count by 10,000,000 … and an event list is exactly where someone reads a
+  number off the screen and types it into something else."
+- The inspector's table is that event list. It now divides `onsetTicksFromFirstRecord` in integers,
+  floors the way the library floors — so the printed time never names an instant later than the
+  event — and keeps the sign a negative onset carries, which EDF+ allows because a recording may
+  begin after its first annotation.
+- The test finds a tick count where the two routes disagree rather than assuming one exists: one
+  tick short of a whole second, at a scale where one tick is below the float's ulp, the float
+  route names the second AFTER the event.
+
+## 0.6.81
+
+- **Fixed** the inspector deciding which events fall in the window it draws by comparing
+  `onsetSecondsFromFirstRecord` against the bounds itself. `annotations-query.ts` exists for that
+  comparison and quotes the expression that was there: "The obvious filter is
+  `a.onsetSecondsFromFirstRecord >= from && … < to`, and those are float64 seconds converted from
+  exact tick counts."
+- Mistake 4 on `AGENTS.md` — "Compare event times in `bigint` ticks, not the floats" — on the page
+  that draws the events and the samples on one axis.
+- It changes two things, not one. The bounds are now converted to ticks once and compared exactly,
+  and the window is HALF-OPEN: the hand-written test used `<=` at the right edge, so an event
+  landing exactly on a window boundary was drawn in that window and in the next one. The test
+  builds a file with an event on every second and shows the old comparison returning three events
+  for a two-second window.
+
 ## 0.6.80
 
 - **Changed** `decodeStatusWord` to refuse a value that is not a BDF sample. It was

package/package.json

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