@nervur.org/genome 0.37.10 → 0.37.11
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/docs/authoring.md +13 -1
- package/docs/changelog.md +18 -9
- package/genome/brain/guide.js +1 -1
- package/genome/faculties/ear/blueprint.js +1 -1
- package/genome/faculties/ear/text.js +1 -1
- package/genome/faculties/library/blueprint.js +1 -1
- package/genome/faculties/library/library.js +16 -2
- package/genome/faculties/library/text.js +1 -1
- package/genome/faculties/mouth/blueprint.js +1 -1
- package/genome/faculties/mouth/text.js +1 -1
- package/genome/faculties/scheduler/blueprint.js +1 -1
- package/genome/faculties/scheduler/text.js +1 -1
- package/package.json +1 -1
- package/standard/version.js +1 -1
package/docs/authoring.md
CHANGED
|
@@ -556,6 +556,15 @@ marked `irreversible` is hinted destructive, and a job is followed as a task whe
|
|
|
556
556
|
passphrase and the salt it names, or by a copy of `boot.key`. The brain's `backup {keys}` adds public keys, as
|
|
557
557
|
`nervur arrive` shows them, whose secrets open it too. A repo with no lobe elsewhere stays behind, and the backup
|
|
558
558
|
names it first: keep a lobe of every repo on a second organism.
|
|
559
|
+
- **A named key from your own secret**, so an app keeps 32 bytes and opens its backups anywhere: HKDF-SHA-256 of the
|
|
560
|
+
secret, with an empty salt, gives 32 bytes under the info `nervur backup key x25519`, the X25519 secret, and 64
|
|
561
|
+
under `nervur backup key ml-kem`, the ML-KEM-768 seeds `d` (the first 32) and `z` (the last 32). The public key is
|
|
562
|
+
the X25519 public key, then the ML-KEM encapsulation key, 1216 bytes, handed as hex to `backup {keys}`. In a faculty:
|
|
563
|
+
`const x = this.crypto.hkdf(secret, this.codec.utf8('nervur backup key x25519'), 32)`, `const m =
|
|
564
|
+
this.crypto.hkdf(secret, this.codec.utf8('nervur backup key ml-kem'), 64)`, then `this.crypto.x25519PublicKey(x)`
|
|
565
|
+
beside `this.crypto.mlkemKeys(m.slice(0, 32), m.slice(32)).encapsulation`; a page or a script does the same with
|
|
566
|
+
any HKDF, X25519 and ML-KEM-768 library. On a new device the same secret opens it: a page's `lay(backup, secret)`,
|
|
567
|
+
or `nervur restore`.
|
|
559
568
|
- **Taking a backup by asks**, from a faculty, an app or afar: `backup` answers at once `{sequence, mark}`, and the
|
|
560
569
|
organism writes on, however large it is. Ask `backupPiece {mark, at, length}` from `at: 0`, each `at` the one before
|
|
561
570
|
plus the bytes it gave: a piece answers once its bytes are written, so no ask waits on the whole. The piece that
|
|
@@ -675,7 +684,10 @@ nervur lobe "$repo" commit '{"message":"reminders"}' --follow
|
|
|
675
684
|
|
|
676
685
|
A `build`, a `pull`, a `push` and an `init` are jobs alike. A pull or a push whose far side hangs is yours to end
|
|
677
686
|
before it stands still for as long as it may: `nervur lobe "$repo" stop` ends it failed, saying it was stopped, unless
|
|
678
|
-
it lands already.
|
|
687
|
+
it lands already. Of each asker the repo lobe and the jailer keep every job that runs and its newest ended, as many as
|
|
688
|
+
one read of the lobe's memory holds, so a lobe that works for years never fills its cells; an older end is answered
|
|
689
|
+
absent. Their lists, `jobs`, the jailer's `folders` and the repo lobe's `told`, answer a page, `{jobs, cursor}` and
|
|
690
|
+
alike: hand `cursor` back to read on, until it is `null`.
|
|
679
691
|
|
|
680
692
|
**Telling a version.** The repo's version is its root `package.json`'s `version`. A commit that raises it is tagged
|
|
681
693
|
`v<version>`, and the tag tells every faculty, organ and design version its commit holds; from then those bytes never
|
package/docs/changelog.md
CHANGED
|
@@ -1,14 +1,23 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.37.
|
|
3
|
+
## 0.37.11
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
for the floor's design, its look as `faculty` and its data as `assets`. The design kit no longer exports `SCREEN_WAY`.
|
|
5
|
+
A repo lobe and the jailer no longer keep every job for ever: of each asker they keep the jobs that run and the newest
|
|
6
|
+
that ended, as many as one read holds, and an older one is answered absent. The update forgets the jobs that ended
|
|
7
|
+
before it.
|
|
9
8
|
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
`jobs`, the jailer's `folders` and a repo lobe's `told` now answer a page, `{jobs, cursor}`, `{folders, cursor}` and
|
|
10
|
+
`{told, cursor}`: hand `cursor` back to read on, until it is `null`. `told` lists versions in the order they were told,
|
|
11
|
+
the newest last, and a library reads it to its end. A scan that lists more parts than one read holds says so in the
|
|
12
|
+
repo lobe's `state`, under `cut`.
|
|
12
13
|
|
|
13
|
-
A repo lobe
|
|
14
|
-
|
|
14
|
+
A repo lobe tells each far library apart: one that does not answer no longer keeps the others from hearing a version.
|
|
15
|
+
|
|
16
|
+
A design's hidden files, such as `.DS_Store`, are no longer counted in its data, so a design folder holding one builds
|
|
17
|
+
the data digest its repo lobe finds.
|
|
18
|
+
|
|
19
|
+
The authoring paper now tells how to draw a backup's named key from a 32-byte secret of your own, in a faculty or a
|
|
20
|
+
page, so the same secret restores it on a new device.
|
|
21
|
+
|
|
22
|
+
The window says when the home's list of faculties holds more than it shows, and says that the organism holds more than
|
|
23
|
+
it read rather than calling a lobe absent.
|