@sjawhar/pi-legion-envoy 5.2.1 → 5.3.1

package/dist/legion.js

@@ -16142,7 +16142,7 @@ import { logger } from "@oh-my-pi/pi-utils";
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "5.2.1",
+  version: "5.3.1",
   type: "module",
   omp: {
     extensions: [
@@ -31484,7 +31484,7 @@ var LegionGoErrorResponse = exports_external.union([
 var legionGoDeliveryView = exports_external.strictObject({
   id: nonEmptyString2,
   task: nonEmptyString2,
-  phase: exports_external.enum(LEGION_GO_PHASES).optional(),
+  phase: exports_external.enum(LEGION_GO_WORKFLOW_PHASES).optional(),
   queuedAt: timestamp,
   deliveredAt: timestamp.optional(),
   confirmedAt: timestamp.optional()

package/dist/skills/legion-worker/SKILL.md

@@ -603,6 +603,28 @@ This publishes your phase's completion to the architect's role and clears the da
 record of this issue's active phase. Do not add pipeline labels, run a controller loop, or
 invent a different completion protocol — this is the whole contract.
 
+**A refused completion is information, not a retry loop.** The daemon attributes your report to
+the run whose task you took, and answers with what it found. What each answer carries, and what to
+do:
+
+- `HANDOFF_STALE_GENERATION` — names the issue, the run it is on, and the run your completion
+  reported. The issue has moved to a newer run since your task was given, so the work you just
+  reported belongs to a run that is over. Nothing you can repeat changes that: stop, push nothing
+  further, and tell the architect what you completed and that its run has been superseded. A task
+  for the current run arrives in this same session if the phase still needs you.
+- `HANDOFF_NOT_CURRENT_PHASE` — names your role, the issue, and the phase it is in now. The issue
+  has left your phase; report to the architect rather than completing again.
+- `HANDOFF_NO_RUN` — names neither: it says this claim has taken no task, so the daemon cannot
+  tell which run you are reporting. Your pane is completing outside any assignment. Say so to the
+  architect; do not re-run the phase.
+- `HANDOFF_ALREADY_RECORDED` — names your role, the phase, the review round and the commit. This
+  exact call was received before, and its first answer stands — accepted, or one of the refusals
+  above. Sending it again changes nothing; if you did not see that first answer, tell the
+  architect so and quote this one.
+
+Quote the answer verbatim in what you tell the architect: with the run and phase it names, the
+difference between "my work is lost" and "my work belongs to the previous run" is visible.
+
 **Stay in this session afterward.** Your process does not exit when your phase completes;
 it goes idle in its pane, and after `worker_idle_retire_seconds` (default 600 s) idle with no
 active phase the daemon retires it — your next assignment resumes this same session from its

package/package.json

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