@sjawhar/pi-legion-envoy 0.32.0 → 0.34.0

package/dist/envoy.js

@@ -30045,7 +30045,7 @@ var LegionDaemonApi = {
     })
   },
   ProcessReady: {
-    request: architectCapability,
+    request: architectCapability.extend({ generation: number2().int() }),
     response: object({})
   },
   MergeGate: {

package/dist/legion.js

@@ -30043,7 +30043,7 @@ var LegionDaemonApi = {
     })
   },
   ProcessReady: {
-    request: architectCapability,
+    request: architectCapability.extend({ generation: number2().int() }),
     response: object({})
   },
   MergeGate: {
@@ -33486,7 +33486,8 @@ function legionExtension(pi) {
         await callReadyWithRetry("root process/ready", () => roleDaemon().processReady({
           tree,
           sessionId: sessionID,
-          secret: started.secret
+          secret: started.secret,
+          generation: generation(process.env)
         }));
         registerArchitectTools();
         await activateLegionTool();

package/dist/skills/dispatch/SKILL.md

@@ -144,8 +144,10 @@ dispatch_comment({ issue, artifact?, quote?, occurrence?, body, reply_to?, reply
 
 It returns `details` `{ issue, topic, comment }`. `quote` requires `artifact`; omit both for a
 floating issue comment. A reply (`reply_to`/`reply_to_ask`) takes no `quote`; it belongs to its
-parent's anchor. Use `reply_to` to continue a comment thread; use `reply_to_ask` to reply
-directly under a question asked with `dispatch_ask`. The two are mutually exclusive.
+parent's anchor. Use `reply_to` to continue a comment thread at its root; a reply to a resolved
+thread reopens it. Use `reply_to_ask` to reply directly under a question asked with
+`dispatch_ask`. The two are mutually exclusive. Comments are edited only by their author from the
+dashboard.
 
 Propose an exact replacement instead of describing it:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion-envoy",
-  "version": "0.32.0",
+  "version": "0.34.0",
   "type": "module",
   "omp": {
     "extensions": [