@sjawhar/claude-envoy 1.4.0 → 1.5.1

package/.claude-plugin/plugin.json

@@ -2,5 +2,5 @@
   "name": "claude-envoy",
   "description": "Deliver Envoy events as Claude Code channel notifications and expose Envoy MCP tools.",
   "mcpServers": "./.mcp.json",
-  "version": "1.4.0"
+  "version": "1.5.1"
 }

package/.omp-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-envoy",
-  "version": "1.4.0",
+  "version": "1.5.1",
   "description": "Deliver Envoy events as Claude Code channel notifications and expose Envoy MCP tools.",
   "mcpServers": {}
 }

package/dist/envoy-channel.js

@@ -52558,8 +52558,8 @@ function createLegionDaemonClient(baseUrl, fetchFn = fetch) {
     return parsed.value;
   };
   const post = (path, request, response, body) => read("POST", path, response, request.parse(body));
-  const acknowledge = async (path, body) => {
-    const { status, text } = await call("POST", path, body);
+  const acknowledge = async (path, body, signal) => {
+    const { status, text } = await call("POST", path, body, signal);
     if (status !== 204 || text !== "") {
       throw new LegionDaemonContractError("POST", path, status, "the route answers 204 with no body");
     }
@@ -52568,7 +52568,7 @@ function createLegionDaemonClient(baseUrl, fetchFn = fetch) {
     state: (options) => read("GET", "/legion/v1/state", LegionStateResponse, undefined, options?.signal),
     register: (input) => read("POST", "/legion/v1/claims/register", LegionRegisterResponse, input),
     registerController: (input) => read("POST", "/legion/v1/claims/register", LegionControllerRegisterResponse, input),
-    ready: (input) => acknowledge("/legion/v1/claims/ready", input),
+    ready: (input, options) => acknowledge("/legion/v1/claims/ready", input, options?.signal),
     readyForUpdate: (input) => acknowledge("/legion/v1/claims/ready-for-update", input),
     exit: (input) => acknowledge("/legion/v1/claims/exit", input),
     activity: (input) => acknowledge("/legion/v1/claims/activity", input),
@@ -55082,7 +55082,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
 
 // package.json
 var name = "@sjawhar/claude-envoy";
-var version2 = "1.4.0";
+var version2 = "1.5.1";
 var legion = {
   daemonApiVersion: 51
 };
@@ -55921,11 +55921,6 @@ async function bootLegionClaim(host) {
     host.stop();
     return;
   }
-  const { measure } = host;
-  const measuring = measure === undefined ? undefined : Promise.resolve().then(() => measure(claim)).catch((error) => {
-    host.log(`capability measurement failed; ready carries no report: ${messageFor(error)}`);
-    return;
-  });
   try {
     await host.afterRegister?.(claim);
     host.setCapability({
@@ -55935,16 +55930,15 @@ async function bootLegionClaim(host) {
       tree: claim.tree,
       issue: claim.issue,
       role: claim.role,
-      secret: claim.secret
+      secret: claim.secret,
+      promptAgents: claim.promptAgents
     });
     await host.claimRole(claim.claimToken);
-    const capabilities = await measuring;
     const ready = {
       claimToken: claim.claimToken,
       sessionId: host.registration.sessionId,
       secret: claim.secret,
-      generation: claim.generation,
-      ...capabilities === undefined ? {} : { capabilities }
+      generation: claim.generation
     };
     await callReadyWithRetry("claims/ready", () => daemon.ready(ready));
     host.onRoleRegained(async (role, reason) => {

package/legion/skills/legion-worker/references/tools.md

@@ -611,15 +611,16 @@ something to count.
   gVisor follows with no error. So code that walks a path one component at a time and opens each
   with `O_NOFOLLOW` is defeated there while every leaf check still passes, and its tests stay
   green on a developer's kernel. A whole block of such tests failing in a pod is that one
-  property of the environment, not one defect per test. The fix shape holds on both kernels: the
-  walk cannot trust the flag, so `lstat` the component, `fstat` the descriptor it opened, compare
-  `st_dev` and `st_ino`, and refuse when they differ or when the `lstat` says `S_IFLNK`.
-  `openat2` is not the alternative there: a lane measured it returning `ENOSYS` under gVisor for
-  every flag combination it tried, so the `lstat` and `fstat` comparison above is the portable
-  check rather than a fallback. The question is not which tool to use but whether anything you
-  run calls `openat2`, which you can read off the binary (two builds of one tool reporting an
-  identical `--version` differed here, and only the package version and the checksum told them
-  apart):
+  property of the environment, not one defect per test. The fix shape holds on both kernels:
+  the walk cannot trust `O_DIRECTORY|O_NOFOLLOW` there, so it opens each component with
+  `O_PATH|O_NOFOLLOW|O_CLOEXEC`, which opens the entry itself on both kernels, and reads the
+  kind from fstat of that handle. The repository's own instance is `mountPointBeneath` in
+  `packages/daemon/internal/launcher/roleinit_linux.go`. `openat2` is not the alternative
+  there: a lane measured it returning `ENOSYS` under gVisor for every flag combination it
+  tried, so the handle rule above is the portable check rather than a fallback. The question
+  is not which tool to use but whether anything you run calls `openat2`, which you can read off
+  the binary (two builds of one tool reporting an identical `--version` differed here, and only
+  the package version and the checksum told them apart):
 
   ```sh
   b=$(readlink -f "$(command -v <tool>)")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/claude-envoy",
-  "version": "1.4.0",
+  "version": "1.5.1",
   "license": "Apache-2.0",
   "description": "Claude Code channel plugin for Legion's Envoy bus",
   "type": "module",