@sjawhar/pi-legion 19.15.0 → 19.15.1

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/legion.js CHANGED
@@ -28544,7 +28544,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
28544
28544
  // package.json
28545
28545
  var package_default = {
28546
28546
  name: "@sjawhar/pi-legion",
28547
- version: "19.15.0",
28547
+ version: "19.15.1",
28548
28548
  license: "Apache-2.0",
28549
28549
  type: "module",
28550
28550
  omp: {
@@ -101,15 +101,18 @@ on the pod, so the round does not wait for it. Its retry is the architect's or t
101
101
  for any failed role, and yours once the architect escalates the hold
102
102
  ([An escalated hold](#an-escalated-hold)). A retried claim is asked like any other.
103
103
 
104
- Before it replaces the pod, the daemon checks every workspace on the pod's disk for work the
105
- remote lacks, a failed claim's included, and pushes what it finds to a rescue branch of its own,
106
- `legion/<KEY>-rescue-<pod>-<n>`. When it pushed one, it writes the issue a message naming each
107
- rescue branch and its commit, for the issue's roles to merge into the issue branch; that message
108
- asks nothing of you. When the check or a push fails for any workspace, the daemon does not replace
109
- the pod, and this wake's `reason` says that the check for unpushed work failed and names the claim
110
- the check ran through, each workspace and its error. Everything else of the pod's disk goes with
111
- the pod: the round's task tells each worker to put any scratch evidence it still needs on Dispatch
112
- before it answers.
104
+ Before it replaces the pod, the daemon checks every workspace on the pod's disk for the issue's
105
+ own work the remote lacks, a failed claim's included, and pushes it to the issue's one rescue
106
+ branch, `legion/<KEY>-rescue`, which only moves forward. When it found work the issue branch
107
+ does not have, it writes the issue a message: a short summary of each branch and its commits,
108
+ and a link to an artifact of the issue with the full list, for the issue's roles to merge into
109
+ the issue branch; that message asks nothing of you. A pod of an older image pushes to branches
110
+ of its own, `legion/<KEY>-rescue-<pod>-<n>`, and its message says so in the same shape. When
111
+ the check or a push fails for any workspace, the daemon does not replace the pod, and this
112
+ wake's `reason` says that the check for unpushed work failed and names the claim the check ran
113
+ through, each workspace and its error. Everything else of the pod's disk goes with the pod: the
114
+ round's task tells each worker to put any scratch evidence it still needs on Dispatch before it
115
+ answers.
113
116
  One round wakes you once, however many sweeps find it open, so handle it when it arrives.
114
117
  Read `read_state` and the issue first, as for every wake: a round that finished since needs
115
118
  nothing.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.15.0",
3
+ "version": "19.15.1",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {