@sjawhar/pi-legion-envoy 1.58.0 → 1.59.0

package/dist/envoy.js

@@ -32251,6 +32251,9 @@ class DispatchClient {
   async syncArchitectureSource(project) {
     return this.#json("POST", ["api", "v1", "projects", project, "architecture-source", "sync"]);
   }
+  async getArchitectureSource(project) {
+    return this.#json("GET", ["api", "v1", "projects", project, "architecture-source"]);
+  }
   async resolveAsk(id, input) {
     return this.#json("POST", ["api", "v1", "asks", id, "resolve"], input);
   }
@@ -32746,6 +32749,20 @@ function componentsChange(input, after) {
       return "components -> inherit";
   }
 }
+var architectureComponentsAction = 'Review the `dispatch` skill, "Architecture components", to attach it to the parts it changes or mark it as non-architectural with a reason.';
+async function architectureGuidance(client, project, components) {
+  if (components.mode === "none" || components.ids.length > 0)
+    return;
+  try {
+    await client.getArchitectureSource(project);
+    return `Project ${project} has an architecture model, but this issue is not linked to any of its current components. ${architectureComponentsAction}`;
+  } catch (error) {
+    if (error instanceof DispatchServiceError && error.status === 404 && error.code === "SOURCE_NOT_FOUND") {
+      return;
+    }
+    return `Could not check whether project ${project} has an architecture model: ${messageFor(error)}. ${architectureComponentsAction}`;
+  }
+}
 function isDuplicateCandidate(value) {
   if (typeof value !== "object" || value === null)
     return false;
@@ -33569,9 +33586,13 @@ async function executeDispatchTool(input) {
           ...Array.isArray(labels) ? { labels } : {},
           actor
         });
-        const adviceLines = renderAdvice(input.tool, created.key, created.advice, {
-          isPrimarySpec: spec !== undefined
-        });
+        const componentGuidance = await architectureGuidance(client, created.project, created.components);
+        const adviceLines = [
+          ...renderAdvice(input.tool, created.key, created.advice, {
+            isPrimarySpec: spec !== undefined
+          }),
+          ...componentGuidance === undefined ? [] : [componentGuidance]
+        ];
         return {
           text: [
             `Created ${created.key}: ${created.title} ${notSubscribed(issueTopic(created.key))}`,

package/dist/legion.js

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

package/dist/skills/dispatch/SKILL.md

@@ -302,7 +302,9 @@ that follow from it:
 the question carries `dispatch://KEY/artifact/<slug>` (or `ref`), never just its filename. Text
 they must read to decide belongs in the spec in the first place — see [Artifacts](#artifacts).
 
-Attach an issue to the architecture components it changes, before decomposing it — children inherit the parent's attachment unless they choose their own, so attaching the root once classifies the whole tree:
+## Architecture components
+
+Attach every architectural issue to the components it changes. Attach the root before decomposing it: children inherit the root's effective attachment unless they deliberately set their own, so one root attachment classifies the whole tree.
 
 ```
 dispatch_issue({ project: "CORE", title: "...", components: { mode: "explicit", ids: ["dispatch-server", "web"] } })
@@ -311,7 +313,9 @@ dispatch_issue_update({ issue: "CORE-13", components: { mode: "none", reason: "h
 dispatch_issue_update({ issue: "CORE-14", components: { mode: "inherit" } })                  // back to the parent chain's attachment
 ```
 
-Component ids are the file names under the repository's `.dispatch/architecture/` (`web.md` → `web`); an id the model lacks, or an `external` component, is refused with `COMPONENTS_INPUT`. A closed issue can be classified without reopening. Two rules: declare and attach before decomposing work, and change code and its architecture description (`.dispatch/architecture/<id>.md`) in the same review — the tree at `GET /api/v1/projects/{key}/architecture` counts every issue whose effective set names a component or anything it contains.
+No native Dispatch tool lists component ids. Read the configured model with `GET /api/v1/projects/{key}/architecture` and use each non-external `components[].id`; when its source repository is your checkout, those ids are the file names under `.dispatch/architecture/` (`web.md` → `web`). An id absent from the model, or an `external` component, is refused with `COMPONENTS_INPUT`.
+
+Use `mode: "none"` with a concrete reason only when the work is genuinely non-architectural (for example hiring, process, or operations work). A closed issue can be classified without reopening. Change code and its architecture description (`.dispatch/architecture/<id>.md`) in the same review.
 
 Import a project's architecture model from its configured source repository now (a human configures the source in Settings):
 ```ts

package/package.json

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