@sjawhar/pi-legion 11.4.0 → 11.5.1

package/dist/legion.js

@@ -4767,6 +4767,7 @@ var CheckoutFileSchema = looseObject({
   $schema: string2().optional(),
   dispatch: DispatchSectionSchema.optional()
 });
+var AskgateSectionSchema = strictObject({ enabled: boolean2().optional() });
 function offWithNotice(notice) {
   return { enabled: false, notice, error: null };
 }
@@ -4975,7 +4976,8 @@ function readEnvoyConfig(filePath, env, options) {
       kind: "valid",
       path: checkoutPath,
       dispatch: checkoutFile.settings.dispatch ?? {},
-      envoyError: Object.hasOwn(checkoutFile.settings, "envoy") ? `${checkoutPath}: envoy is not read from a checkout's envoy.json; put it in ${filePath}` : null
+      envoyError: Object.hasOwn(checkoutFile.settings, "envoy") ? `${checkoutPath}: envoy is not read from a checkout's envoy.json; put it in ${filePath}` : null,
+      askgateError: Object.hasOwn(checkoutFile.settings, "askgate") ? `askgate in ${checkoutPath} is not read; set it in ${filePath}` : null
     };
   }
   const oldCheckout = path.resolve(options.cwd, ".opencode", "envoy.json");
@@ -6705,6 +6707,11 @@ import {
 } from "fs";
 import { homedir as homedir2 } from "os";
 import { join as join2 } from "path";
+
+// ../envoy-client/src/askgate-marker.ts
+var MARKER_MAX_AGE_MS = 2 * 60 * 60000;
+
+// ../envoy-client/src/dispatch-session-state.ts
 var SESSION_ID = /^[A-Za-z0-9._-]{1,128}$/;
 var PRIVATE_DIR = 448;
 var PRIVATE_FILE = 384;
@@ -8151,7 +8158,7 @@ async function bootLegionClaim(host) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "11.4.0",
+  version: "11.5.1",
   license: "Apache-2.0",
   type: "module",
   omp: {

package/dist/skills/legion-architect/references/design-gate.md

@@ -51,12 +51,13 @@ When the gate is armed, run this exact sequence before the tree's work starts:
    them to answer: give such a point its own decision block first, or take it out of the spec.
 
    ```bash
-   dispatch request-approval --issue <root issue> --summary '<what the human is approving> Reviews: <gap result>, <claim result>.'
+   dispatch request-approval --issue <root issue> --summary '<what the human is approving> Reviews: <gap result>, <claim result>; <what they do not show>.'
    ```
 
    `--summary` says in one to three sentences what the human is approving and nothing else (no
-   commentary and no open question), then one sentence with both reviews' results, for example
-   `Reviews: no open gap, 14 of 14 claims verified.` The primary document is the default; the
+   commentary and no open question), then one sentence with both reviews' results and what they do
+   not show, for example `Reviews: no open gap, 14 of 14 claims verified; neither shows that the
+   design works once built.` The primary document is the default; the
    command prints `Approval requested for spec.md (document id <UUID>) at version <N> (ask <id>)`.
 5. Register that document version with the daemon:
 

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

@@ -82,7 +82,7 @@ missing proof goes back as step 1 says. The Dispatch message (step 7) is for a f
    Dispatch's message limit, and ends with your attribution footer:
 
    ```bash
-   dispatch message --issue "$LEGION_ISSUE" --body-file - <<'EOF'
+   dispatch message --issue '<KEY>' --body-file - <<'EOF'
    ## Retro Complete
 
    **Learnings documented in:** docs/solutions/<path>.md, or none: <why no point qualified>.

package/dist/skills/legion-worker/references/findings.md

@@ -157,13 +157,13 @@ takes. That issue,
 it](#when-no-controller-takes-it) says:
 
 ```bash
-dispatch comment --issue <ASK KEY> --body-file - <<'EOF'
+dispatch comment --issue '<ASK KEY>' --body-file - <<'EOF'
 <the evidence: commands, output with its time, file:line, links>
 EOF
 # Keep `File it for Legion` only when your Legion addressing line lists the repository where the
 # fix belongs. For a clear defect no controller took, replace the `File an issue` option below with
 # 'Hand it to the owning tree: <the tree, when you know it>', the first option and recommended.
-dispatch ask --issue <ASK KEY> --ref 'dispatch://<ASK KEY>/comment/<id>' --question-file - \
+dispatch ask --issue '<ASK KEY>' --ref 'dispatch://<ASK KEY>/comment/<id>' --question-file - \
   --option 'File an issue: <what it would track, and who would own it>' \
   --option 'File it for Legion: Legion works it once it is filed' \
   --option 'Do not file: <what stays as it is>' <<'EOF'

package/package.json

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