edfcore 0.4.256 → 0.4.257

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.256";
112
+ export declare const VERSION = "0.4.257";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.256';
82
+ export const VERSION = '0.4.257';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.257
10
+
11
+ - **Fixed** `AGENTS.md`'s description of the layering, which had been wrong about nearly every
12
+ tier. It sketched six — "`bytes`/`text` → `diagnostics` → `header`/`decode`/`tal` → `time` →
13
+ `io` → entry points" — where the declarations use eight, and grouped modules that are not
14
+ together: `bytes` is layer 0 and `text` is layer 1, `header`, `decode` and `tal` are three
15
+ different layers rather than one, and `io` spans two. 0.4.256 reasoned from that sentence to
16
+ correct a module's layer, which is a good argument for the sentence being right. It is now a
17
+ table of the eight, and says plainly that each module's own declaration is the source of truth
18
+ rather than a second definition.
19
+ - **Added** a check that the summary names the layers that exist, and that the count in the
20
+ sentence above it matches. Only the numbers are compared — a prose list of members is the
21
+ inventory problem this project keeps deleting, and the declarations already answer membership.
22
+ What a summary can still get wrong unnoticed is the shape: a tier added or removed in one place
23
+ and not the other.
24
+
9
25
  ## 0.4.256
10
26
 
11
27
  - **Corrected** `src/tal/ticks.ts` from layer 3 to layer 1, and started enforcing the direction
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.256",
3
+ "version": "0.4.257",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.256';
96
+ export const VERSION = '0.4.257';