@xema/omni-protocol 0.1.50 → 0.1.51

package/dist/validation.js

@@ -1796,6 +1796,16 @@ export function validateTaskCommand(command, task, path = "command") {
     }
     if (!isPlainObject(task))
         return into.violations;
+    // The task the command is held to has to be one the wire published. A host's own mapping of it,
+    // handed in for want of the original, is not, and checking a command against it would be
+    // checking against a task nobody has -- so the task is validated first, and a command is held
+    // only to a task that stands.
+    const published = new Collector();
+    validateTaskInto(task, { channel: channel ?? "voice" }, `${path}.task`, published);
+    if (published.violations.length > 0) {
+        into.add("command.task", `${path}.task`, `the task the command is held to is not one the wire published (${published.violations.map(v => v.rule).join(", ")}): pass the task as the provider sent it, or validate the command's shape alone`);
+        return into.violations;
+    }
     // What the task has to offer or be in for the command to be issuable.
     const capabilities = isPlainObject(task.capabilities) ? task.capabilities : {};
     const offered = (name) => {

package/guide.md

@@ -3887,7 +3887,13 @@ declared:
 | Everything else | Its own named capability. |
 
 `validateTaskCommand(command, task)` holds a command to this table at runtime, both ways: the
-capability it needs, the phase it belongs to, and the state that has to stand.
+capability it needs, the phase it belongs to, and the state that has to stand. The task it wants
+is the one the provider published, not a host's own mapping of it: a host that keeps only its
+mapped shape has nothing honest to pass, and then checks shape alone, which is still worth doing
+-- it names a command the wire never had -- but is not the table. Keeping the published task
+beside the mapped one is what the full check costs a host; an adapter has it for free. The
+validator holds a command only to a task that stands: a task handed in that is not one the wire
+published is named (`command.task`) rather than checked against.
 
 Declining or rejecting a pending offer ends it without accepting or completing it. The provider
 confirms the end with `task-ended` and a `cancelled` outcome.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xema/omni-protocol",
-  "version": "0.1.50",
+  "version": "0.1.51",
   "description": "The Omni protocol: the contract every provider adapter implements",
   "type": "module",
   "license": "MIT",