@sjawhar/pi-envoy 10.9.1 → 10.9.3

package/dist/dispatch.js

@@ -16574,6 +16574,18 @@ function dispatchRefFromUrl(value, serverUrl) {
 }
 var refGrammarProblem = "ref must be a valid dispatch:// reference such as dispatch://KEY-1, " + "dispatch://KEY-1/ask/<uuid>, dispatch://KEY-1/comment/<uuid>, " + "dispatch://KEY-1/message/<uuid>, dispatch://KEY-1/artifact/<slug>, " + "dispatch://PROJECT/artifact/<document-ref> (an artifact id, slug, or filename), or " + "dispatch://agent/<session id>/artifact/<slug> (a picture in a conversation on the Agents page, " + "for dispatch doc-read); a dashboard URL on this Dispatch server is accepted too";
 var ownerRequiredProblem = "issue is required; supply issue or set LEGION_ISSUE";
+function innerRefProblem(tool, ref, refText) {
+  if (ref.kind !== "ask" && ref.kind !== "comment" && ref.kind !== "message")
+    return;
+  if (tool === "dispatch_read" || tool === "dispatch_ask")
+    return;
+  const owner = refOwnerName(ref);
+  const documentTool = tool === "dispatch_suggest" || tool === "dispatch_doc_edit";
+  const ownerArguments = ref.owner.kind === "issue" ? `issue ${ref.owner.issue}${documentTool ? " and artifact <the document's slug>" : ""}` : `project ${ref.owner.project} and artifact ${ref.artifact}`;
+  const fix = tool === "dispatch_comment" && ref.kind === "ask" ? `reply under it with reply_to_ask ${ref.id} and ${ownerArguments}` : tool === "dispatch_comment" && ref.kind === "comment" ? `reply in its thread with reply_to ${ref.id} and ${ownerArguments}` : `read it with dispatch read, or name ${owner} with ${ownerArguments}`;
+  const item = ref.kind === "ask" ? "an ask" : `a ${ref.kind}`;
+  return `ref ${refText} names ${item} on ${owner}; dispatch ${commandName(tool)} would act on ${owner} and drop the ${ref.kind}: ${fix}`;
+}
 var toolSchemas = new Map;
 function toolSchema(tool) {
   const cached2 = toolSchemas.get(tool);
@@ -16609,6 +16621,10 @@ async function resolveOwnerArguments(tool, input, cwd, env, exec, dashboardUrls,
     ref = parseDispatchRef(refText);
     if (ref === null) {
       problems.push(tool === "dispatch_ask" && !refText.startsWith("dispatch://") ? "ref must be a dispatch:// reference" : refGrammarProblem);
+    } else {
+      const inner = innerRefProblem(tool, ref, refText);
+      if (inner !== undefined)
+        problems.push(inner);
     }
   }
   const issueArgument = args.issue;

package/dist/skills/dispatch/SKILL.md

@@ -71,7 +71,7 @@ not share this session's vocabulary, and is often on a phone. Write for that per
 - Before posting, test it: could the human, reading only this text on their phone, know what they are being
   told or asked? If not, rewrite it. Length is not the problem; density is.
 - When an ask or message communicates a judgment, lead with that judgment in one sentence and put the mechanism underneath it. Do not make the reader ask a second time whether the result is a win. This shapes communication only when a judgment exists; it does not pre-decide an open question or remove its genuine options.
-- When a Dispatch message states a root cause, include the reproducing command or test in that same message. Without it, label the diagnosis a hypothesis; a diagnosis still in progress may say so plainly. This boundary applies to causal claims, not to reporting that an investigation has started.
+- When an ask, comment or message states a root cause or a blocker, include the command, error output or record that shows it, with its time, in that same text. Without it, label the diagnosis a hypothesis; a diagnosis still in progress may say so plainly. This boundary applies to causal claims, not to reporting that an investigation has started.
 
 ## Writing a spec
 
@@ -157,7 +157,7 @@ Labels are optional: Dispatch trims them, preserves their case, and removes case
 the new key; creating an issue does not subscribe you to it (see [Following](#following)). Use `dispatch issue` only to create an issue; never use it to park a question. When you pass a spec,
 follow [Writing a spec](#writing-a-spec).
 
-When the work needs a project that does not exist yet, create it yourself with `dispatch project --key <KEY> --name '<name>'`; nobody has to make it by hand. Projects cannot be renamed or deleted, so a mistyped key stays for good: check the keys that exist first with `dispatch projects`. A key that already exists is refused with `PROJECT_EXISTS`.
+Work goes in a project that exists: `dispatch projects` lists them, and work that spans projects goes in the one that owns most of it. Create a project only when the human asks for one, with `dispatch project --key <KEY> --name '<name>'`. Projects cannot be renamed or deleted, so a mistyped key stays for good. A key that already exists is refused with `PROJECT_EXISTS`.
 
 ## Search first
 
@@ -272,7 +272,7 @@ instead of pointing at another message in prose (below), is the asking session's
 Open a standalone ask with `dispatch ask` (`dispatch ask --help` lists its flags), one `--option` per choice:
 ```bash
 dispatch ask --issue <KEY> --question-file - --option 'Label: what it costs' --option 'Other: what it costs' <<'EOF'
-<the problem, what constrains the answer, and your recommendation with its reason>
+<the problem, what constrains the answer (each answer of his you rely on, linked), and your recommendation with its reason>
 EOF
 ```
 It prints the ask's id; you follow the ask you opened (see [Following](#following)).

package/dist/skills/dispatch/references/documents.md

@@ -79,6 +79,9 @@ dispatch comment --issue <KEY> --artifact spec --quote '<the passage>' --body '<
 It prints the comment's id; a `--reply-to-ask` reply also makes you one of the ask's followers
 (see [Following](skill://dispatch/references/asks.md)).
 `--ref` names the owner (an issue or project-document reference) in place of `--issue`/`--project`.
+An ask, comment or message link there is refused, since the comment would land outside it: reply
+under an ask with `--reply-to-ask`, in a comment's thread with `--reply-to`, and read a message
+with `dispatch read`.
 `--quote` requires `--artifact`; its anchor is pinned to the containing block while retaining the quote
 for display. Omit both for a floating issue comment. A reply (`--reply-to`/`--reply-to-ask`) takes no
 `--quote`; it belongs to its parent's anchor. Reply to any comment in a thread; the server keeps

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-envoy",
-  "version": "10.9.1",
+  "version": "10.9.3",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {