@sjawhar/pi-legion-envoy 1.8.0 → 1.8.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.
|
@@ -105,9 +105,10 @@ idea what the fuck you're talking about."
|
|
|
105
105
|
Then park. Do not release a wave or spawn a Legion role until a later delivered wake
|
|
106
106
|
shows `design-approved` on the root. On a deployment whose design gate is off
|
|
107
107
|
(`gates.design: off` in its `legion.yaml`), the daemon satisfies the gate as you register it
|
|
108
|
-
and `design-approved` arrives immediately — proceed
|
|
109
|
-
|
|
110
|
-
integration-failure children do not repeat
|
|
108
|
+
and `design-approved` arrives immediately — proceed. The daemon then closes the ask on Dispatch
|
|
109
|
+
(you will see `ask.resolved` for it); that is expected and needs nothing from you. Approval
|
|
110
|
+
covers the entire tree: later waves, re-scopes, and integration-failure children do not repeat
|
|
111
|
+
this sequence.
|
|
111
112
|
|
|
112
113
|
## 2. Children in flight
|
|
113
114
|
|