researchclaw-async-run-id-polling-pattern-for-long-pipelines
AutoResearchClaw pipeline invocations are long-running (23 stages, minutes to hours). The correct MCP integration pattern is for researchclaw_run to return immediately with a run_id, with progress polled via researchclaw_status and artifacts retrieved via researchclaw_get_output. Synchronous blocking calls will timeout for any non-trivial research task. This async pattern mirrors how Observatory and MiroFish handle long-running operations.