@sjawhar/pi-legion 10.7.0 → 10.7.2

package/dist/legion.js

@@ -16171,7 +16171,7 @@ function ompCapabilityHost() {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "10.7.0",
+  version: "10.7.2",
   license: "Apache-2.0",
   type: "module",
   omp: {

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

@@ -248,17 +248,15 @@ gh pr comment <pr-number> \
 ## Planner artifact
 
 The plan lives in `.legion/<issue>/plan.json` and the issue's `plan.md` document, never in the issue's
-primary document, which is its spec; never commit a plan or spec file to the repository.
-No `docs/plans/*`, `docs/superpowers/plans/*`, or spec markdown goes into the pull request: plan
-and spec content goes into the issue, never into a PR (the root `AGENTS.md`
-calls its own `docs/plans/` human-authored design history, not a Legion artifact). A skill step that says "save the plan
-to a file" is satisfied by the handoff write in the completion gate below; the planner's only
-commit is `plan: record handoff`.
+primary document, which is its spec. Legion sets no rule on whether a plan or spec goes in the
+repository: the planner commits a plan, a spec or spec code when the issue, its spec or the
+repository asks for it. Otherwise, a skill step that says "save the plan to a file" is satisfied by
+the handoff write in the completion gate below.
 
 A plan that departs from the spec's design records the departure in `plan.md` and in the required
 `.legion/<issue>/plan.json` `specDepartures`: `[]` means no departure; otherwise each bounded record names
 the spec, plan, evidence and outcome. The planner's role prompt defines that record. The planner
-never edits the spec. Whether the spec changes is the architect's decision
+never edits the issue's spec document. Whether the spec changes is the architect's decision
 (`skill://legion-architect`, section 1), and the reviewer reads the plan beside the spec.
 
 ## Implementer push and pull request

package/package.json

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