@sjawhar/pi-legion-envoy 7.9.1 → 7.9.3

package/dist/legion.js

@@ -18031,7 +18031,7 @@ function endInjectedUserTurns(sessionID) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "7.9.1",
+  version: "7.9.3",
   license: "Apache-2.0",
   type: "module",
   omp: {

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

@@ -386,7 +386,11 @@ It pushes `@-` through the provisioned credential helper, which authenticates as
 which pushes skip CI and which commit-message keywords it refuses. While the head commit carries
 `skip-checks: true`, a pull-request body edit alone starts no GitHub workflow run, so a check that
 re-judges the body re-runs on that head only after a later push; on a code head the same edit
-re-runs it at once. Its ancestry check refuses
+re-runs it at once. While the pull request conflicts with its base (GitHub shows it
+`CONFLICTING`), no workflow triggered `on: pull_request` runs for any of its activity types, so
+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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion-envoy",
-  "version": "7.9.1",
+  "version": "7.9.3",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {