@nervur.org/genome 0.37.3 → 0.37.5

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
@@ -669,7 +669,9 @@ its code:
669
669
  nervur lobe "$repo" commit '{"message":"reminders"}' --follow
670
670
  ```
671
671
 
672
- A `build`, a `pull`, a `push` and an `init` are jobs alike.
672
+ 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
673
+ before it stands still for as long as it may: `nervur lobe "$repo" stop` ends it failed, saying it was stopped, unless
674
+ it lands already.
673
675
 
674
676
  **Telling a version.** The repo's version is its root `package.json`'s `version`. A commit that raises it is tagged
675
677
  `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,17 +1,22 @@
1
1
  # Changelog
2
2
 
3
- ## 0.37.3
3
+ ## 0.37.5
4
4
 
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.
5
+ Pushes and pulls are reliable again. Since 0.37.4, a repo lobe that checked on a job in the very second the job ended
6
+ took it for lost, its end still on its way, so a push or a pull that had in fact landed was reported failed: the push
7
+ had moved the far `main`, yet the next push, finding nothing left to send, said it landed while the far repo still
8
+ answered its old head. A check now never guesses: the jailer keeps the end it last told each repo lobe, and the lobe
9
+ takes that end, whole, from its letter or from its check, whichever comes first. Only a job the jailer no longer holds
10
+ ends as lost.
9
11
 
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.
12
+ A repo now always answers the head its `main` stands at: each scan that ends whole keeps the head it read. On
13
+ updating, a repo whose head stood behind its `main` answers it again within a minute, after the scan the update owes;
14
+ nothing is lost, and nothing needs pushing again.
14
15
 
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.
16
+ A pull or a push whose far side hangs no longer holds its repo until the time it may stand still passes:
17
+ `nervur lobe <repo> stop` ends it at once, failed, saying it was stopped, its owner's or its asker's to ask. One that
18
+ lands already is refused, since it ends landed.
19
+
20
+ An MCP call no longer waits without end on a node busy with other asks: it answers within a minute, at most, an error
21
+ naming the node it reached and saying that what it asked may still take effect, so a model reads that node before it
22
+ asks again. Work longer than that is a job, answered at once, as before.