The workbook the run executed against — settled before rendering, exactly as renderMarkdown requires.
Optionaloptions: Renderer.OptionsThe registry pass-through IS the default — run -e "wb" answers with the workbook report,
which is the whole reason a separate describe verb is unnecessary. Strings pass through as
markdown (a script that formatted its own answer), any renderable SDK object dispatches through
the renderer registry, and plain data (a getValues() array) renders as a bare value grid.
Anything with no renderer gets a ONE-LINE summary — never a structure dump, which is what a
host's raw/JSON affordance is for. Only an undefined result is silent.
Shared by every transport that returns a result: the CLI's run printout, the MCP run tool,
and the webview executing against an attended session — one ladder, so the same expression answers
identically everywhere.
Renders a run's result value — the final expression of a snippet, or a script's return value.