wise-workflow-runlisted

# /wise-workflow-run - the conductor Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. First read [host control](../../references/workflow-host-control.md). Resolve the loaded installation, set `WISE_HOST` to this conductor and `WISE_PLUGIN_ROOT` to that installation. Use its managed launcher for shell commands. Follow the reference's diagnostics and explicit-answer fallback when MCP or a native picker is unavailable. Conductor host and child provider are independent. The `wise_*` tools (`wise_status`, `wise_preflight`, `wise_run`, `wise_wait`, `wise_answer`, `wise_cancel`, `wise_nudge`, `wise_resume`) come from the managed `wise-engine` MCP server; Claude Code shows them with a server prefix. Errors return `{"error":{code,message,...}}`. ## Arguments `$ARGUMENTS`: first token is the workflow name (empty: run `"$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" list-defs`, pick with AskUserQuestion plus Abort). Remaining tokens fill the declared inputs in order; the last declared input absorbs the rest of the line. ## 1. Init check Call `wise_status` (no id). Workflows do not read the session profile set by `/wise-profile`; pre-flight asks harness, provider permissions, model and effort instead. - `wise_*` tools missin