edfcore 0.4.281 → 0.4.283
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +32 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.4.283";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,38 @@ 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.283
|
|
10
|
+
|
|
11
|
+
- **Added** a check that the sidebar order is a total order. `content.config.ts` requires `section`
|
|
12
|
+
and `order` on every page so "a new page cannot silently land at the bottom of the wrong group",
|
|
13
|
+
and it cannot require the thing that makes the order deterministic: that no two pages in a
|
|
14
|
+
section share a number. `DocsNav.astro` sorts by it and `Array.prototype.sort` is stable, so a
|
|
15
|
+
tie falls back to whatever order the collection loader returned — a filesystem detail. Two pages
|
|
16
|
+
would swap places between machines and nobody would call it a bug, because nothing said what the
|
|
17
|
+
right order was.
|
|
18
|
+
- The same numbers are the reading order `llms.txt` and `llms-full.txt` hand an agent, which is
|
|
19
|
+
where a tie stops being cosmetic: "the guides, in order" is the only structure those files have.
|
|
20
|
+
Titles and descriptions are checked for uniqueness for the same reason — both are addresses
|
|
21
|
+
rather than prose, and two pages sharing either are two pages a reader cannot tell apart from
|
|
22
|
+
outside. Contiguous numbering is checked as well, which is a judgement rather than a rule: a gap
|
|
23
|
+
breaks nothing, and it is what a deleted page leaves behind.
|
|
24
|
+
|
|
25
|
+
## 0.4.282
|
|
26
|
+
|
|
27
|
+
- **Fixed** the corpus manifest calling one field two names. Five of the seven entries recorded
|
|
28
|
+
what a file is for under `exercises` and two under `purpose`, and `tests/README.md` names only
|
|
29
|
+
the second: the manifest "records the URL, byte size, SHA-256, licence and purpose of each
|
|
30
|
+
file". Nothing read either — that field exists to be read by a person deciding whether a 48 MB
|
|
31
|
+
download is worth it — so the split had no symptom until something asked all seven entries the
|
|
32
|
+
same question.
|
|
33
|
+
- **Added** the check that asked. The manifest is the provenance record on which this repository
|
|
34
|
+
is willing to pull 59 MB of other people's recordings onto a contributor's machine: the hash is
|
|
35
|
+
what makes the download reproducible, the licence is where permission is written down, and three
|
|
36
|
+
of these entries record "no licence stated" together with why that is acceptable. Every field the
|
|
37
|
+
README names is now required, digests are checked for shape — 64 lowercase hex — because
|
|
38
|
+
checking the value needs the file, which is the thing this suite refuses to require, and a URL
|
|
39
|
+
has to be one the fetcher could resolve.
|
|
40
|
+
|
|
9
41
|
## 0.4.281
|
|
10
42
|
|
|
11
43
|
- **Checked** that `sideEffects: false` is honest, rather than merely present. 0.4.230 read the
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED