@nervur.org/genome 0.37.4 → 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 +3 -1
- package/docs/changelog.md +16 -21
- 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/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
|
@@ -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,27 +1,22 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.37.
|
|
3
|
+
## 0.37.5
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
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.
|
|
8
11
|
|
|
9
|
-
A repo
|
|
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.
|
|
10
15
|
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
end lost, held the repo for good. Now such a job ends as lost; where the jailer saw it end whole, the files it
|
|
15
|
-
committed stay and the repo is scanned again.
|
|
16
|
-
- A scan owed stopped its own alarm once it began, so nothing looked at it again. Its alarm now rings each minute
|
|
17
|
-
until a scan ends whole, and each ring checks the job. A pull or a push waiting on a job of its repo does the same,
|
|
18
|
-
where before it checked once and waited.
|
|
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
19
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
A phone's app builds again. Capacitor finds a plugin's Swift package by the name it makes of the plugin's npm name,
|
|
25
|
-
which for `@nervur.org/installer-phone` is `Nervur.orgInstallerPhone`; the package still bore the name of its old
|
|
26
|
-
scope, `NervurOrgInstallerPhone`, so `cap sync` named a package that stood nowhere and Xcode refused the app. The
|
|
27
|
-
package and its library now bear the new name; an app takes it by updating the package and running `cap sync` again.
|
|
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.
|