@sjawhar/pi-legion 10.17.1 → 10.18.1

package/dist/legion.js

@@ -14754,11 +14754,11 @@ var dispatchToolSpecs = [
   {
     name: "dispatch_read",
     example: { issue: "DSP-1" },
-    description: "Read an issue or project-document summary, targeted ask, or targeted comment reply chain, or the conversation " + "a message belongs to. Do not use it for document contents; use dispatch doc-read instead. Supply ref, issue, " + "or project plus artifact; or message alone, which reads a human's direct message to this session and every " + "reply to it (they belong to no issue). " + "An anchored comment or ask also says where its quote sits, as `Position:`: the block's path from the top, " + "and in a table the row (0 is the header), the cells before the anchored one, and the column's header; " + "`Position: unavailable (<code>)` when Dispatch could not read the document: `DOC_SERVICE_UNAVAILABLE` " + "(try again shortly), `DOC_SCHEMA` (the document needs repair), `DOCUMENT_UNLOADABLE` (the document " + "needs a rebuild) or `INTERNAL`. " + "An issue read carries a `Progress:` line, `tasks 3/7, children 2/5`: its spec's task-list items " + "(`- [ ]` / `- [x]`, nested lists included) and its direct children, each done of total and each only " + "when it has any (`Progress: none` otherwise). " + "Every read ends with `Referenced by:` (what cites or hangs off this node, each with its dispatch:// address, " + "an excerpt, and when) and `Links:` (what it cites), so tracing provenance is one call. " + "The pictures the shown messages, asks and comments embed come back as images you see, newest first, at most 8 " + "and 10 MiB of them per read, each a PNG, JPEG, GIF or WebP of at most 3,750,000 bytes (5 MB of base64); a `Pictures:` section names each " + "one shown, in order, and the rest by reference, for dispatch doc-read. A picture this session was already shown is named, not sent again " + "(every request carries the session's history, and the provider refuses one over 32 MB); dispatch doc-read shows it again. " + OWNER_REFERENCE,
+    description: "Read an issue or document summary, targeted ask, or targeted comment reply chain, or the conversation " + "a message belongs to. Do not use it for document contents; use dispatch doc-read instead. Supply ref, issue, " + "issue plus artifact (one of its documents), or project plus artifact; or message alone, which reads a human's direct message to this session and every " + "reply to it (they belong to no issue). A document summary names its issue, reference, versions and approval. " + "An anchored comment or ask also says where its quote sits, as `Position:`: the block's path from the top, " + "and in a table the row (0 is the header), the cells before the anchored one, and the column's header; " + "`Position: unavailable (<code>)` when Dispatch could not read the document: `DOC_SERVICE_UNAVAILABLE` " + "(try again shortly), `DOC_SCHEMA` (the document needs repair), `DOCUMENT_UNLOADABLE` (the document " + "needs a rebuild) or `INTERNAL`. " + "An issue read carries a `Progress:` line, `tasks 3/7, children 2/5`: its spec's task-list items " + "(`- [ ]` / `- [x]`, nested lists included) and its direct children, each done of total and each only " + "when it has any (`Progress: none` otherwise). " + "Every read ends with `Referenced by:` (what cites or hangs off this node, each with its dispatch:// address, " + "an excerpt, and when) and `Links:` (what it cites), so tracing provenance is one call. " + "The pictures the shown messages, asks and comments embed come back as images you see, newest first, at most 8 " + "and 10 MiB of them per read, each a PNG, JPEG, GIF or WebP of at most 3,750,000 bytes (5 MB of base64); a `Pictures:` section names each " + "one shown, in order, and the rest by reference, for dispatch doc-read. A picture this session was already shown is named, not sent again " + "(every request carries the session's history, and the provider refuses one over 32 MB); dispatch doc-read shows it again. " + OWNER_REFERENCE,
     arguments: (z2) => ({
       issue: z2.string().describe(ISSUE_REFERENCE).optional(),
       project: z2.string().describe("Project key owning the document.").optional(),
-      artifact: z2.string().describe("Project document artifact id, slug, or filename.").optional(),
+      artifact: z2.string().describe("Document artifact id, slug, or filename: one of the issue's, or a project document.").optional(),
       ref: z2.string().describe("Optional dispatch:// issue or document reference.").optional(),
       message: z2.string().describe("A message id (uuid): reads the conversation it belongs to, the root message and every " + "reply. Name nothing else with it.").optional()
     }),
@@ -15803,6 +15803,10 @@ var legionCapabilityState = exports_external.strictObject({
   configLine: nonEmptyString.optional(),
   source: exports_external.enum(["configuration", "boot"]).optional()
 });
+var legionSettings = exports_external.looseObject({
+  max_fix_attempts: exports_external.number().int().positive(),
+  worker_boot_timeout_seconds: exports_external.number().int().positive()
+});
 var legionCacheView = exports_external.strictObject({
   repo: nonEmptyString,
   sandbox: nonEmptyString,
@@ -15836,7 +15840,8 @@ var LegionStateResponse = exports_external.strictObject({
   controllerLocator: legionControllerLocator.optional(),
   agentSecretsLogin: legionAgentSecretsLoginView.optional(),
   capabilities: exports_external.array(legionCapabilityState),
-  repositories: legionRepositories
+  repositories: legionRepositories,
+  settings: legionSettings
 });
 var LegionRegisterResponse = exports_external.strictObject({
   claimToken: nonEmptyString,
@@ -16913,7 +16918,7 @@ async function bootLegionClaim(host2) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "10.17.1",
+  version: "10.18.1",
   license: "Apache-2.0",
   type: "module",
   omp: {
@@ -16925,7 +16930,7 @@ var package_default = {
     ]
   },
   legion: {
-    daemonApiVersion: 34
+    daemonApiVersion: 35
   },
   repository: {
     type: "git",

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

@@ -24,12 +24,13 @@ the owner a command names (`-R owner/repo`, `repos/owner/repo` in `gh api`, a Gi
 the first owner's (`GH_CONFIG_DIR`) otherwise, so name the repository. Against a daemon with no
 GitHub App, `legion controller start` says so when it starts (`[legion] the daemon has no GitHub
 App to act as; the controller's gh acts as nobody`), and `gh` acts as nobody. The controller reads
-Dispatch and the daemon's state, and applies its controller
-capability, through the `legion` tool alone: `op: "read_state"` returns the daemon's whole state
-(`issues.<KEY>.phase`, `issues.<KEY>.holdReason`, `issues.<KEY>.architect`, `admission.cap`,
-`admission.active`, `admission.waiting`, `capabilities[]`, `daemon.project`), and `op: "set_status"`
-with `issue` and `status` (`todo`, `backlog` or `icebox`) moves an issue. It runs no `legion` from
-bash. Any pull-request comment or review the controller posts ends with
+Dispatch and the daemon's state, and applies its controller capability, through the `legion` tool
+alone: `op: "read_state"` returns the daemon's whole state (`issues.<KEY>.phase`,
+`issues.<KEY>.holdReason`, `issues.<KEY>.architect`, `admission.cap`, `admission.active`,
+`admission.waiting`, `capabilities[]`, `daemon.project`, and `settings`, how the daemon is tuned:
+its resolved `legion.yaml`, `max_fix_attempts` and the rest, with no credential in it, LEGION-791),
+and `op: "set_status"` with `issue` and `status` (`todo`, `backlog` or `icebox`) moves an issue. It
+runs no `legion` from bash. Any pull-request comment or review the controller posts ends with
 `<!-- legion: {"session":"<session-id>","phase":"controller"} -->`, the footer every Legion role
 appends: the daemon reads the session to tell a controller's review from the reviewer's verdict. A
 review the controller submits without that footer still decides nothing for Legion's own workflow
@@ -495,4 +496,3 @@ controller never opens a gate and there is no operator command for it; a project
 want the gate at all runs `gates.design: off` in its `legion.yaml`. Otherwise resolve the
 authoritative owning architect role and route the verified context with `envoy_publish`. Do not
 route raw event traffic or invent a role token from a partial issue reference.
-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion",
-  "version": "10.17.1",
+  "version": "10.18.1",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {
@@ -12,7 +12,7 @@
     ]
   },
   "legion": {
-    "daemonApiVersion": 34
+    "daemonApiVersion": 35
   },
   "repository": {
     "type": "git",