@sjawhar/pi-legion-envoy 5.3.4 → 5.3.6

package/dist/envoy.js

@@ -34402,7 +34402,7 @@ function subscriptionRemovedTopics(raw, sessionID) {
 
 // ../envoy-client/src/tool-contract.ts
 var DELIVERY_CONTRACT = "Delivery is at-least-once, possibly out of order across topics; use id for dedupe and at for freshness.";
-var TOPIC_GUIDE = "Topic guide (all are under notifications.): agent.<session_id> (subscribe: own inbox); role.<role> " + "(publish-to; holders claim via envoy_role_set). > matches one or more trailing tokens and does not " + "match the base subject. Envoy registers the concrete base when you subscribe to <subject>.>, so " + "the recommended default remains github.<owner>.<repo>.pr.<n>.>. Default PR subscription: " + "github.<owner>.<repo>.pr.<n>.> (it receives the quiet PR family): pr.<n> (lifecycle: " + "opened/synchronize/closed; closed carries merged, merge_commit_sha, merged_by, head_sha), " + "pr.<n>.comment, pr.<n>.review, pr.<n>.mention, pr.<n>.checks (one head-checks settlement event: " + 'passed/failed/cancelled/skipped with failing names and URLs; re-fires with superseded_settlement: "true" ' + "when new runs appear for the same head). Other GitHub: issue.<n>, issue.<n>.comment, " + "issue.<n>.mention, mention, push.branch.<name>, push.tag.<name>, workflow.<file>.<action> (only " + "runs without an associated PR); slack.<team>.<channel>.message|mention and " + "slack.<team>.<channel>.thread.<ts>.message|mention; ghostwispr.<session>.<kind>; " + "whatsapp.<phone>.<jid>.<kind>; envoy.exceptions.<original-topic>.";
+var TOPIC_GUIDE = "Topic guide (all are under notifications.): agent.<session_id> (subscribe: own inbox); role.<role> " + "(publish-to; holders claim via envoy_role_set). > matches one or more trailing tokens and does not " + "match the base subject. Envoy registers the concrete base when you subscribe to <subject>.>, so " + "the recommended default remains github.<owner>.<repo>.pr.<n>.>. <owner> and <repo> are one token " + "each, with every dot in the name written _ (sjawhar/.github is github.sjawhar._github; " + "acme/site.io is github.acme.site_io), and a topic spelled with the dot receives nothing. " + "Default PR subscription: " + "github.<owner>.<repo>.pr.<n>.> (it receives the quiet PR family): pr.<n> (lifecycle: " + "opened/synchronize/closed; closed carries merged, merge_commit_sha, merged_by, head_sha), " + "pr.<n>.comment, pr.<n>.review, pr.<n>.mention, pr.<n>.checks (one head-checks settlement event: " + 'passed/failed/cancelled/skipped with failing names and URLs; re-fires with superseded_settlement: "true" ' + "when new runs appear for the same head). Other GitHub: issue.<n>, issue.<n>.comment, " + "issue.<n>.mention, mention, push.branch.<name>, push.tag.<name>, workflow.<file>.<action> (only " + "runs without an associated PR); slack.<team>.<channel>.message|mention and " + "slack.<team>.<channel>.thread.<ts>.message|mention; ghostwispr.<session>.<kind>; " + "whatsapp.<phone>.<jid>.<kind>; envoy.exceptions.<original-topic>.";
 var URGENCY_VALUES = EnvelopeSchema.shape.urgency.unwrap().options;
 var EXPECTS_REPLY_VALUES = EnvelopeSchema.shape.expects_reply.unwrap().options;
 function messageMetadataShape(schema) {

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.3.4",
+  version: "5.3.6",
   type: "module",
   omp: {
     extensions: [

package/dist/skills/envoy/SKILL.md

@@ -18,6 +18,10 @@ envoy_subscribe([
 ])
 ```
 
+The owner and the repository are one token each, with every dot in the name written `_`:
+`acme/site.io`'s PR family is `notifications.github.acme.site_io.pr.42.>`, and a topic spelled
+`acme.site.io` receives nothing.
+
 NATS `>` matches **one or more** trailing tokens, so it does not match the lifecycle base
 `pr.42` itself. Envoy registers that concrete base automatically when you subscribe to
 `<subject>.>`, making `pr.<n>.>` the recommended default: one call receives both the lifecycle
@@ -137,7 +141,10 @@ envoy_subscribe([
 
 A warning says no GitHub event for that repository occurred within the stream's 72-hour retention
 window; it does not mean the repository was never seen. Verify the GitHub App is installed before
-relying on a wakeup.
+relying on a wakeup. A topic that spells a repository name with its dot, followed by a kind, draws
+a warning naming the spelling Envoy publishes (`acme.site_io` for `acme/site.io`); subscribe to
+that one instead. A token after the repository that is not a GitHub topic kind (`checks` in
+`acme.widgets.checks.>`) draws a warning naming the kinds.
 
 ## Roles
 

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

@@ -611,16 +611,22 @@ do:
   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.
+  for the current run arrives in this same session if the phase still needs you. The same answer
+  comes when your turn started before the daemon recorded the current run's task as yours, so it
+  still holds you to the earlier run: that task is sent again. When a task arrives, do what it
+  asks; if the work it asks for is already committed, call `handoff_complete` again, and never redo
+  the work or write a second handoff.
 - `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.
+  exact call was received before, and its first answer stands: accepted, or a refusal the daemon
+  records with the call — `HANDOFF_STALE_GENERATION`, `HANDOFF_NOT_CURRENT_PHASE`,
+  `READY_REQUIRED` or `HANDOFF_NOT_NEW`. `HANDOFF_NO_RUN` is never that first answer, since it is
+  given before anything is recorded. 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.

package/package.json

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