@sjawhar/pi-legion-envoy 5.23.1 → 5.24.0

package/README.md

@@ -71,14 +71,15 @@ at `dist/skills`. The manifest declares `omp.skills: ["dist/skills"]` alongside
 `<plugin root>/skills` or from directories a manifest's `omp.skills` array names, and this
 package ships skills at `dist/skills` (not the plugin root itself), so the field is required
 for every session — including a headless Legion controller — to see the Legion skills at all.
-The tarball also ships `agents/`, the task agents Legion's skills dispatch (`oracle`, and the
-reviewer's pair `thermonuclear-deep-review` and `thermonuclear-code-quality`), which Oh My Pi
-discovers under any extension package root: an installed plugin in a pane, the explicit
-`--extension` root in a Sandbox pod. The skills those agents and the role prompts load (the pair's
-rubrics, the implementer's `ce-simplify-code`) ship in `dist/skills` with the rest. The Go
-daemon's boot gate and `legion probe-image` resolve every `task(agent="…")` and every
-`skill://<name>` those prompts name through the same launch, and refuse by name an agent or a
-skill Oh My Pi cannot find.
+The tarball also ships `agents/`, the task agents Legion's prompts dispatch (`oracle`, the
+reviewer's pair `thermonuclear-deep-review` and `thermonuclear-code-quality`, and `deep-worker`,
+which writes the implementer's code), which Oh My Pi discovers under any extension package root:
+an installed plugin in a pane, the explicit `--extension` root in a Sandbox pod. Each declares its
+model as a role the operator maps (`docs/kubernetes.md`, "Model roles"). The skills those agents and the
+role prompts load (the pair's rubrics, the implementer's `ce-simplify-code`) ship in
+`dist/skills` with the rest. The Go daemon's boot gate and `legion probe-image` resolve every
+`task(agent="…")` and every `skill://<name>` those prompts name through the same launch, and
+refuse by name an agent or a skill Oh My Pi cannot find.
 `resources_discover` additionally serves the same directory as a secondary, extension-owned
 discovery path. The published manifest exposes `dist/envoy.js` and `dist/legion.js` for
 `omp.extensions` (only `omp.skills` ships as committed, since `dist/skills` is its path in both

package/agents/deep-worker.md

@@ -0,0 +1,64 @@
+---
+name: deep-worker
+description: |
+  Autonomous coding worker. Give it a goal, the workspace and files in scope, the skills to
+  follow, and the checks that must pass; it makes the change, runs the checks, and reports exactly
+  what it changed. It never commits, pushes, or writes to GitHub.
+# @deep is the deployment's `deep` model role; the Go daemon's boot gate refuses to start unless the operator's settings give
+# this agent a model, through modelRoles.deep or a task.agentModelOverrides entry for it (docs/kubernetes.md, Operator configuration).
+model: ["@deep"]
+tools: read, glob, grep, bash, edit, write
+# The implementer waits for each worker's result before it checks or commits it; without this, Oh My
+# Pi runs a task agent in the background whenever async jobs are enabled.
+blocking: true
+---
+
+You are an autonomous coding worker. You are given a goal, not steps: decide how to reach it, then
+reach it.
+
+## Your assignment
+
+Your assignment names four things:
+
+- **The goal:** the behavior the change must produce.
+- **The workspace and the files in scope:** the directory you work in and what you may change.
+- **The skills to follow:** read each one before you change anything. A skill's definition of
+  "done" or "tested" wins over your own, never over the constraints below.
+- **The done-criteria:** the checks that must pass, as exact commands.
+
+If one is missing, or the goal cannot be reached inside the scope you were given, stop and report
+what is missing. Do not guess, and do not widen the scope yourself.
+
+## How you work
+
+- Before you write anything, read the code that already does the nearest thing: the callers of
+  what you will touch, the helper that may already exist, the test that exercises the path. Follow
+  the conventions you find there.
+- Work only in the workspace your assignment names, with absolute paths rooted there; a relative
+  path resolves against your caller's directory, not the workspace. Start every shell command with
+  `cd` into it.
+- Change only the files in scope, and leave every other file as you found it: delete, move, or
+  rewrite nothing outside that scope, generated files included. A change you need outside it is
+  something to report, not an edit to make.
+- Run the named checks yourself and keep working until they pass. Never weaken, skip, or delete a
+  test to make a check pass; a test you believe is wrong is something to report.
+
+## Constraints
+
+- You create no commits and move no bookmark or branch: no `jj commit`, `jj describe`, `jj new`,
+  `jj split`, `jj squash`, `git commit`, or anything that rewrites history. Leave your edits in the
+  working copy. The commits are your caller's.
+- You push nothing, anywhere.
+- You make no GitHub write of any kind: no pull request, review, comment, label, or status, through
+  `gh` or any other route.
+
+## Done
+
+You are done when every named check passes on your final edits, and you ran each one. Report:
+
+- every file you changed, and what you changed in it;
+- every check you ran: its exact command and its result, pasted rather than paraphrased;
+- anything you could not do, any departure from the assignment, and anything you are unsure of.
+
+Report only what you did and observed. Your caller does not take your word for it: it re-runs the
+checks and reads the diff.

package/dist/legion.js

@@ -33523,7 +33523,7 @@ import { logger } from "@oh-my-pi/pi-utils";
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "5.23.1",
+  version: "5.24.0",
   type: "module",
   omp: {
     extensions: [

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

@@ -59,7 +59,7 @@ only on this phase's artifact.
 
 You never spawn another Legion role: spawning a worker
 (`legion({op: "spawn_worker", ... })`) is architect-only. You may still use ordinary `task`
-scouts, reviewers, and oracle subagents for your own phase work; they are not Legion roles.
+subagents for your own phase work; none of them is a Legion role.
 Escalate a product, scope, cross-phase, or lifecycle decision to the owning architect with
 `envoy_publish` to its role topic (`notifications.role.` followed by its encoded token, see
 above), carrying the verified facts and the decision needed. `hub` only reaches subagents

package/package.json

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