@sjawhar/pi-legion-envoy 1.22.0 → 1.22.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.
|
@@ -18,7 +18,11 @@ separate coordinator to finish necessary work.
|
|
|
18
18
|
Message a known phase worker with `envoy_publish` to `notifications.role.` followed by
|
|
19
19
|
its encoded role token (the token `spawn_worker` returned for it); re-assign it by
|
|
20
20
|
calling `spawn_worker` again on the same existing role, which resumes the same process
|
|
21
|
-
instead of starting a fresh one.
|
|
21
|
+
instead of starting a fresh one. Phases on one issue are strictly sequential -- one role
|
|
22
|
+
is the issue's active phase at a time, and calling `spawn_worker` for a different role
|
|
23
|
+
while a phase is active supersedes that phase: the superseded worker's
|
|
24
|
+
`legion handoff complete` is then refused, so finish (or deliberately abandon) one role
|
|
25
|
+
before assigning the next. Phase workers escalate lifecycle, scope, and
|
|
22
26
|
cross-phase matters the same way: `envoy_publish` to your own encoded token. Any role
|
|
23
27
|
may use `dispatch_ask` directly for a standalone human question; replies return to the
|
|
24
28
|
asking session.
|