@nervur.org/genome 0.37.2 → 0.37.3

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 CHANGED
@@ -156,9 +156,9 @@ nervur install
156
156
  nervur state
157
157
  ```
158
158
 
159
- `nervur install` takes the package from the registry your npm names, npm's own by default, and the organism moves
160
- itself as new versions come: it asks that registry as it starts and every hour. `--channel <registry>` names another
161
- registry for one install or update, a mirror of your own, and the organism then asks that one.
159
+ `nervur install` takes the package from the registry your npm names, npm's own by default. `--channel <registry>`
160
+ names another registry for one install or update, a mirror of your own. The organism never updates itself: a new
161
+ version lands when you run `nervur update`, or ask `upgrade` from afar.
162
162
 
163
163
  Where Node belongs to root, make npm's global folder your account's first: `npm config set prefix ~/.nervur/installer`,
164
164
  with `~/.nervur/installer/bin` on your `PATH`.
@@ -499,7 +499,8 @@ always take a far anchor back by dropping it.
499
499
  so a secret stays out of the shell's history:
500
500
  `nervur lobe <repo> setToken '{"name":"NPM_TOKEN"}' --text value=token.txt`. `--json` prints each answer as data, for
501
501
  programs. `--follow`, on `ask` and `lobe`, waits for the end of a job the answer names, printing the job whole and
502
- exiting on its code. `--home <folder>` names another organism's folder, for tests.
502
+ exiting on its code. `--home <folder>` names a test's organism, under the host's temporary folder alone: an account
503
+ holds one organism, in its home, and the command refuses a second anywhere else.
503
504
 
504
505
  ### The brain's asks
505
506
 
@@ -590,14 +591,10 @@ own guide.
590
591
  itself as a trial with the world held, which writes nothing of the store but its log and the values it lays, and
591
592
  keeps it or brings the old back by itself, so an update copies nothing of the store, whatever its size; that boot
592
593
  moves the installer's organs and the lobes on its faculties, and the update says what moved and what stayed, run
593
- again where one stayed. It is the same on a
594
- machine no one is present at, laid with `--claim`. A version older than the one running is a move onto it. From
595
- afar: `upgrade {version, digest}`. Until 1.0.0 every organism updates itself too: its process asks the registry it was
596
- laid from or last updated by, npm's own unless `--channel` named another for an act, as it starts and every hour, and
597
- runs `nervur update` onto a newer version, its outcome in `organism.log`; one laid from a package at hand
598
- (`--package`) has no channel and checks nothing. A start, a trial and a stop wait on the process's silence, so an
599
- organism whose store takes long to open is waited for. A browser and a phone try each version at its first boot
600
- the same way, an edge when laid again.
594
+ again where one stayed. It is the same on a machine no one is present at, laid with `--claim`. A version older than
595
+ the one running is a move onto it. From afar: `upgrade {version, digest}`. Nothing else moves it: an organism never
596
+ updates itself. A start, a trial and a stop wait on the process's silence, so an organism whose store takes long to
597
+ open is waited for. A browser and a phone try each version at its first boot the same way, an edge when laid again.
601
598
  - **The way back** always stands: `nervur stop`, then `nervur start --floor`, lays the console and window the installer
602
599
  ships, whatever skin was chosen, and the window wears the installer's design again, whatever design was worn: the
603
600
  design lobe that was worn stands, and is worn again from the home.
package/docs/changelog.md CHANGED
@@ -1,17 +1,17 @@
1
1
  # Changelog
2
2
 
3
- ## 0.37.2
3
+ ## 0.37.3
4
4
 
5
- An update copies nothing of the store any more. The new version is tried on the store itself, held: while it is tried
6
- it writes only the store's log and the values it lays, never the database, never a value that stood and never the
7
- store's witness, so the log as it stood is the whole way back. Before, a machine's update copied the whole store for the
8
- trial, which cost nothing only on a disk that clones and cost the store's size in time and space everywhere else, ext4
9
- and NTFS among them, and refused an update on a disk without room for a second store; a browser, a phone and an edge
10
- copied every file of theirs too. Now the way back is the log alone, a few megabytes at most and nothing after a clean
11
- stop, on every host. A trial failed or cut lays the log back as it stood, and what the trial laid goes at the next boot.
12
- Only an organism whose store a release below the floor last ran, which that release opens first, still has its store
13
- laid aside and copied, since that release writes it in place.
5
+ An organism no longer updates itself. Before, its process asked its registry as it started and every hour, and moved
6
+ onto any newer version by itself; now a version lands only where its owner names it, by `nervur update` on the
7
+ machine or `upgrade` from afar, and nothing in the organism asks for a newer one. The file `organism.channel` it kept
8
+ for that is gone.
14
9
 
15
- A boot no longer reads every page of the store to find which values out of line are still named: it reads them by the
16
- index the store keeps for exactly that, so a boot costs what the references hold, not the store's size, and a page that
17
- reads not elsewhere in the store no longer refuses the boot, faulting only what reads it.
10
+ The floor rises to 0.37.2, and no installer carries an older release any more. Before, an update of an organism below
11
+ the floor walked it through each older floor's release, laying its store aside and copying it for them; now a store,
12
+ a backup or a move from below 0.37.2 is refused as it stands, nothing opened: update it to 0.37.2 first, then to this
13
+ version. Every organism on 0.37.2 updates as before.
14
+
15
+ An account holds one organism. Before, `--home` laid an organism in any folder, so one account could run several,
16
+ each able to read every other's keys and store; now `--home` names a test's organism and is refused outside the
17
+ host's temporary folder. A second organism takes an account of its own.
package/docs/guide.md CHANGED
@@ -360,25 +360,18 @@ the version boots with the world held, and it is kept or the old comes back by i
360
360
  organism but its stop, so it moves one no one is present at as it moves one owned at its console. Until 1.0.0 it is
361
361
  abrupt: a run the body has going is lost to it as to a crash, and its lobe told so. What the installer ships, its
362
362
  organs' halves and its faculties, moves at the new version's first boot, a lobe an owner moved to a later version
363
- staying. From afar `upgrade` names a version and its digest, and nothing else lands. Until 1.0.0 every organism also
364
- moves itself to the newest: its process asks the channel it was laid from or last updated by as it starts and every
365
- hour, and runs the same update onto a newer version, saying what it did in its log and asking no one; one laid from a
366
- package at hand has no channel and checks nothing. A start, a trial and a stop wait on the organism's silence, never on
367
- a span: while it opens or ends it tells it lives, so a store that takes long to open is waited for, and a process that
368
- tells nothing for the longest wait, or ends unasked, fails the step with why.
363
+ staying. From afar `upgrade` names a version and its digest, and nothing else lands. An organism never moves itself:
364
+ a version lands only where an owner names it, and nothing asks for a newer one on a clock. A start, a trial and a
365
+ stop wait on the organism's silence, never on a span: while it opens or ends it tells it lives, so a store that takes
366
+ long to open is waited for, and a process that tells nothing for the longest wait, or ends unasked, fails the step
367
+ with why.
369
368
 
370
369
  Two moves stand apart. A faculty's new version is its author's: its `migrate` converts its own cells by its own logic,
371
370
  and Nervur only runs it. Nervur's own new version knows no faculty, and from 1.0.0 breaks no contract one stands on.
372
371
  Until 1.0.0 Nervur goes forward only: a genome names its floor, `FLOOR`, the oldest release whose store it carries
373
- forward, and refuses a store a genome below it last booted, saying to move to the floor first. Until every organism has
374
- crossed it, one `nervur update` carries an organism whatever release it runs: below the floor, the floor's own package
375
- opens its store in place first, then the newest version tries it; a step that fails brings the old back by itself, and
376
- the update says why. On a machine, `nervur update` walks the floors in turn, and a backup from below the floor is
377
- restored by the floor's own release, then updated. Each floor carries its own, so no machine's organism is stranded,
378
- however long it slept. A browser and a phone carry no earlier release beside their files: their floor is the release a
379
- site or an app serves, so a store a release below the genome's floor kept, and a backup or a move laid there that a
380
- release below it wrote, is refused as it stands, saying the installer carries no floor, nothing opened and the store
381
- untouched.
372
+ forward, and refuses a store a genome below it last booted, saying to move to the floor first: update it to the
373
+ floor's release, then to the newest. No installer carries an older release to do that for you, so a store, a backup
374
+ or a move from below the floor is refused as it stands, nothing opened and the store untouched.
382
375
 
383
376
  ## The floor and the licence
384
377
 
@@ -4,7 +4,7 @@ import { } from '#faculty';
4
4
  import { EAR_SOURCE, LIBRARY_SOURCE, MOUTH_SOURCE, SCHEDULER_SOURCE } from '../defaults/index.js';
5
5
  import { keysOf, makeWard, wardSeed, } from '#quo';
6
6
 
7
- import { carryReferences, keepGenome, layGenome, owned, sharePresent, unreadRows } from '../brain/index.js';
7
+ import { keepGenome, layGenome, owned, sharePresent, unreadRows } from '../brain/index.js';
8
8
 
9
9
  import { forgiveLetters, writeDurable, } from '../carry/index.js';
10
10
  import { PAGE } from '../cells/index.js';
@@ -196,7 +196,6 @@ export const boot = async (
196
196
  if (gear.stays === true) written(cells.delete(['moved']));
197
197
  const backwards = keepGenome(cells);
198
198
  if (backwards !== null) return backwards;
199
- carryReferences(cells);
200
199
  const map = mapOf(cells);
201
200
  const library = cellsOf(cache, LIBRARY, true);
202
201
  const shelves = { brain: cells, library };
@@ -3,6 +3,6 @@ import { type Cells } from '#cage';
3
3
  export declare const isLater: (one: string, other: string) => boolean;
4
4
  export declare const genomeIn: (cells: Cells) => string;
5
5
  export declare const layGenome: (cells: Cells) => void;
6
- export declare const FLOOR = "0.33.0";
6
+ export declare const FLOOR = "0.37.2";
7
7
  export declare const BELOW_FLOOR = "below the floor";
8
8
  export declare const keepGenome: (cells: Cells) => null | Why;
@@ -27,7 +27,7 @@ export const genomeIn = (cells ) => {
27
27
 
28
28
  export const layGenome = (cells ) => putRow(cells, ROW, GENOME_VERSION, 'brain');
29
29
 
30
- export const FLOOR = '0.33.0';
30
+ export const FLOOR = '0.37.2';
31
31
 
32
32
  export const BELOW_FLOOR = 'below the floor';
33
33