call capability with deployment id

2026-05-18 01:22:35 +07:00
parent 8fcc66c90c
commit 9e7f91a223
4 changed files with 76 additions and 3 deletions
@@ -223,6 +223,10 @@ A client authoring workflows, including an LLM client, should be able to:
 5. inspect the normalized output and outcome
 6. reuse that capability inside a graph

+Saved wrapper artifacts can be called with a deployment id when they use logical
+source names. The deployment supplies the concrete source bindings for that
+test call, matching the way `run_deployment` resolves a full saved workflow.
+
 That direct-call surface is different from:

 - calling the raw upstream MCP tool