@sjawhar/opencode-legion-envoy 5.0.0 → 5.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "5.0.0",
+  "version": "5.0.1",
   "type": "module",
   "main": "dist/src/server.js",
   "exports": {

package/skills/AGENTS.md

@@ -21,6 +21,6 @@ event intake, process lifecycle, credentials, and role delivery.
 The owning skill above is where each contract is defined; a role prompt that needs a contract from its own seat points there or restates only its own step. This file lists and does not restate.
 A Legion prompt (a skill here, a role prompt, or an agent definition in `packages/pi-envoy/agents/`) names a task agent only as `task(agent="<name>")` and a skill it tells the model to load only as `skill://<name>`. Those are the two forms the Go daemon's boot gate and `legion probe-image` resolve through Oh My Pi, refusing by name one it cannot find; a dispatch or a load written any other way goes unchecked. An agent or skill Legion's prompts name is shipped here or in `packages/pi-envoy/agents/`, unless Oh My Pi bundles it.
 A skill file an agent loads stays under 51,200 bytes, Oh My Pi's spill threshold (a longer one arrives with its middle cut out), and a skill's detail lives in `references/` files linked as `skill://<name>/references/<file>.md`, never by relative path, which a read by path cuts at 300 lines. `packages/pi-envoy/src/skills-guard.test.ts` fails on a file at the threshold, on any `SKILL.md` body of 500 lines or more, on a skill whose frontmatter `name` is not its directory's name, on a `dispatch-first` over its budget, on a `skill://<name>/<path>` link that names a missing file or a missing `#heading`, and on a `legion-worker` reference nothing links.
-The text a worker boots with (its role prompt) lives in `packages/pi-envoy/roles/` and is
-composed per role in `packages/daemon/src/daemon/processes.ts`; `packages/pi-envoy/roles/roles.test.ts`
-holds the structural rules for those parts.
+The text a worker boots with (its role prompt) lives in `packages/daemon/internal/prompts/roles/`,
+embedded in the `legion` binary and composed per role by `packages/daemon/internal/prompts/prompts.go`;
+`packages/daemon/internal/prompts/roles_test.go` holds the structural rules for those parts.

package/skills/legion-worker/SKILL.md

@@ -317,7 +317,7 @@ line), the full definition of a proof, what the tester verifies, and the simplif
 ## Completion gate: handoff write, verification, and persistence
 
 The merger writes no handoff and pushes nothing, so this gate does not apply to it
-(`packages/pi-envoy/roles/merger.md`).
+(`packages/daemon/internal/prompts/roles/merger.md`).
 
 Write the phase-specific handoff: call the `legion` tool with `op: "handoff_write"`, `phase: "<p>"`,
 and `data`: a JSON object of the phase-specific fields only. It runs `legion handoff write` in

package/skills/legion-worker/references/merge-gate.md

@@ -73,12 +73,12 @@ completion leaves the issue in reviewing until you finish.
   in READY (an empty output is quoted as `no file changes above the approved head`); then the same
   with `'~docs/solutions'` appended, which must print nothing. *The READY packet*: the merger
   always posts `READY #<n> at <current sha> (approved at <approved sha>) for <KEY> (<pr url>)`
-  (the shape `packages/pi-envoy/roles/merger.md` defines), then the PR body's `Outcome:` line and
-  its `Not proven / risk:` value — every bullet under that label joined with `; ` on the one
-  READY line, or `none` — quoted from the `## For the reviewer` block at that same head (or one
-  line saying the body carries no brief — the packet still publishes), then the `--summary`
-  output and the PR body's gate facts, as a `dispatch_message` on the issue. When the `Legion
-  addressing` line names a merge queue, it also publishes the same packet there with
+  (the shape `packages/daemon/internal/prompts/roles/merger.md` defines), then the PR body's
+  `Outcome:` line and its `Not proven / risk:` value — every bullet under that label joined with
+  `; ` on the one READY line, or `none` — quoted from the `## For the reviewer` block at that same
+  head (or one line saying the body carries no brief — the packet still publishes), then the
+  `--summary` output and the PR body's gate facts, as a `dispatch_message` on the issue. When the
+  `Legion addressing` line names a merge queue, it also publishes the same packet there with
   `envoy_publish`; a 404 means the Dispatch message remains the durable notice and the merger
   stays idle. The READY packet names both the implementer's and tester's `E2E` lines; a missing
   one is reported to the architect instead of published. Legion never merges.