@sjawhar/pi-legion 8.7.1 → 8.9.0

package/dist/legion.js

@@ -15309,7 +15309,7 @@ function onEnvoyRoleRegained(listener) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "8.7.1",
+  version: "8.9.0",
   license: "Apache-2.0",
   type: "module",
   omp: {
@@ -15321,7 +15321,7 @@ var package_default = {
     ]
   },
   legion: {
-    daemonApiVersion: 17
+    daemonApiVersion: 18
   },
   repository: {
     type: "git",

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

@@ -156,16 +156,16 @@ before new work: anything unpushed is gone. That message stays in history; recon
 - **Before pushing, check ancestry:** `jj -R "$LEGION_WORKSPACE" log -r 'ancestors(@, 5)'`
   — verify only your issue's commits are in the chain, not unrelated work.
 
-**Shared operation safety:** Every Legion issue workspace is a `jj workspace` of one shared
-clone, so they all share one operation log: `jj undo`, `jj abandon`, and
-`jj op restore|revert|abandon|undo` rewrite it for every tree at once. The extension refuses them in every
-phase-worker pane before they run — a `bash` command in any position of a pipeline or `&&`
-chain, with or without `-R`, judged on the whole argument list (a supervised service's start
-included); `eval` code; and stdin written to a service (a `write` to `proc://<id>`) — from your
-own tool calls and from any `task` subagent you spawn (it runs in your pane, against the same
-log), and a `bash` command whose quoted text merely mentions `jj`
-with one of those words (a heredoc, an echo, a commit message) is refused too: write such text
-with the `write` tool or say "operation-log rollback" instead. `jj restore <paths>`,
+**Shared operation safety:** Under tmux every issue workspace is a `jj workspace` of one shared
+clone and operation log; under Kubernetes each issue pod has its own, shared by that issue's roles
+alone. Either way `jj undo`, `jj abandon`, and `jj op restore|revert|abandon|undo` rewrite a log
+other agents work in. The extension refuses them in every phase-worker pane before they run — a
+`bash` command in any position of a pipeline or `&&` chain, with or without `-R`, judged on the
+whole argument list (a supervised service's start included); `eval` code; and stdin written to a
+service (a `write` to `proc://<id>`) — from your own tool calls and from any `task` subagent you
+spawn (it runs in your pane, against the same log), and a `bash` command whose quoted text merely
+mentions `jj` with one of those words (a heredoc, an echo, a commit message) is refused too: write
+such text with the `write` tool or say "operation-log rollback" instead. `jj restore <paths>`,
 `jj op log`, and `jj op show` stay allowed. Recover forward only: a new commit
 (`jj -R "$LEGION_WORKSPACE" new`) or `jj -R "$LEGION_WORKSPACE" restore <paths>` of files.
 Anything else, stop and send the owning architect the `jj -R "$LEGION_WORKSPACE" log`
@@ -398,9 +398,9 @@ re-runs it at once. While the pull request conflicts with its base (GitHub shows
 a body edit re-judges nothing there either; a push cures both, but only once the pull request is
 mergeable, so the implementer forward-merges a conflicting one first (*Reintegrating the base* in
 `skill://legion-worker/references/conflicts-and-rewrites.md`). Its ancestry check refuses
-unless `@-` descends from `legion/<KEY>@origin` (or the branch is not on GitHub yet): every issue
-workspace shares one clone, so another role's push moves `legion/<KEY>@origin` here at once, and
-a push that did not descend from it would move the remote branch sideways onto your commit and
+unless `@-` descends from `legion/<KEY>@origin` (or the branch is not on GitHub yet): your issue's
+roles share one clone (under tmux every issue does), so another role's push moves the remote branch
+here at once, and a push not descending from it would move it sideways onto your commit and
 drop theirs. A handoff commit never sits on an implementer's unpushed chain: when the issue moves
 back to planning, the implementer's unpushed commits stay off the bookmark until the implementer
 returns, and the planner writes its handoff on the remote tip.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion",
-  "version": "8.7.1",
+  "version": "8.9.0",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {
@@ -12,7 +12,7 @@
     ]
   },
   "legion": {
-    "daemonApiVersion": 17
+    "daemonApiVersion": 18
   },
   "repository": {
     "type": "git",