@sjawhar/pi-legion-envoy 1.4.0 → 1.4.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.
|
@@ -91,8 +91,11 @@ legion({ op: "register_gate", issue: "<root issue>", askId })
|
|
|
91
91
|
```
|
|
92
92
|
|
|
93
93
|
Then park. Do not release a wave or spawn a Legion role until a later delivered wake
|
|
94
|
-
shows `design-approved` on the root.
|
|
95
|
-
|
|
94
|
+
shows `design-approved` on the root. On a deployment whose design gate is off
|
|
95
|
+
(`gates.design: off` in its `legion.yaml`), the daemon satisfies the gate as you register it
|
|
96
|
+
and `design-approved` arrives immediately — proceed; the ask remains open on Dispatch as the
|
|
97
|
+
record and needs no answer. Approval covers the entire tree: later waves, re-scopes, and
|
|
98
|
+
integration-failure children do not repeat this sequence.
|
|
96
99
|
|
|
97
100
|
## 2. Children in flight
|
|
98
101
|
|