Workflows: tool-node output is delivered at $.result, not the documented $.toolResult.result — doc-built pins silently resolve undefined

[TenSpy-ai]

Summary

In actual workflow runs, a tool node's output is delivered at $.result, but the plugin/workflow documentation describes it at $.toolResult.result. Pins and data references built from the documented path resolve undefined — silently, since undefined inputs don't error at wiring time.

Reproduction (verified 2026-08-06)

1. Tool node → downstream node with a pinned input using sourcePath per the docs: $.toolResult.result... → resolves undefined at run time.
2. Same pin with $.result... → resolves the tool output correctly.
3. Inspecting run step data confirms the output object sits under result with no toolResult wrapper.

Expected

Either the docs updated to $.result, or the run-time envelope aligned with the documented $.toolResult.result. Silent undefined resolution makes this expensive to diagnose — a validation warning on unresolvable sourcePath would also help (related: #17 area of result-delivery validation).

Built/observed via the Clay plugin's workflow MCP (edit_node) + CLI on Claude Code.