@plurnk/plurnk-execs 1.8.0 → 1.9.0

package/README.md

@@ -52,7 +52,7 @@ tag independently. A name uses lowercase URI-scheme syntax
 `[a-z][a-z0-9+.-]*`; `only` is reserved by runtime policy. `summary` is the
 one-line capability description. `invocation` defines the body and optional
 target buckets plus one canonical example used for dispatch enforcement and the
-generated `worker://plurnk/tools/` document. A `docs/<tag>.md` file supplies
+generated `worker://~/_plurnk/tools/` document. A `docs/<tag>.md` file supplies
 supplemental detail. See {§executor-runtime-declaration}.
 
 ### Implement the executor

package/SPEC.md

@@ -68,6 +68,15 @@ interface ExecArgs {
     ): Promise<string>;
 }
 
+`ExecArgs` deliberately carries **no Worker identity**: an executor is a
+worker-agnostic capability, and `run` may assume nothing about which Worker,
+Loop, or workspace invoked it beyond the arguments given. A runtime whose
+behavior depends on a Worker — an attached MCP server, a Worker Functionality
+manager — is published per Worker by its owning module, closing over that
+identity at publication ({§functionality-model-projection} in the core
+specification; the MCP host is the precedent). Consumers must not smuggle
+identity through `env` or `body` conventions.
+
 interface RuntimeAvailability {
     available: boolean;
     detail?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-execs",
-    "version": "1.8.0",
+    "version": "1.9.0",
     "description": "Framework + contract for the @plurnk/plurnk-execs-* runtime executor packages.",
     "keywords": [
         "plurnk",
@@ -51,8 +51,8 @@
         "prepublishOnly": "npm audit --audit-level=moderate && npm test"
     },
     "dependencies": {
-        "@plurnk/plurnk-contracts": "1.8.0",
-        "@plurnk/plurnk-meta": "1.8.0",
-        "@plurnk/plurnk-schemes": "1.8.0"
+        "@plurnk/plurnk-contracts": "1.9.0",
+        "@plurnk/plurnk-meta": "1.9.0",
+        "@plurnk/plurnk-schemes": "1.9.0"
     }
 }