Run MainDriver outside node event loop

[nasif-z]

Summary

• Run MainDriverApi.main() in the default executor from RunProcess.
• Wrap the async MainDriver entrypoint with asyncio.run() inside the worker thread so the coroutine is executed.
• Keep the node CLI event loop available for service callbacks, install polling, and local server tasks while MainDriver performs blocking work.

[riz-hossain]

🔎 ZeuZ PR Review

Open the full report in ZeuZ: Review findings and apply suggestions

Overview	Value
Agents	✅ 4 completed
Suggestions	💡 2

Agent breakdown

→ General Review

Status: ✅ Completed
Suggestions: 0 suggestions

No actionable issues found in the diff; the change cleanly moves MainDriverApi.main off the node CLI event loop without introducing an obvious correctness regression.

→ Security Review

Status: ✅ Completed
Suggestions: 0 suggestions

No security findings in this PR diff. The change only moves MainDriverApi.main execution off the event loop and does not introduce new input handling, auth, or data exposure risks.

→ Performance Review

Status: ✅ Completed
Suggestions: 1 suggestion

The change correctly moves MainDriverApi.main off the node event loop, but it introduces a per-run thread hop plus a fresh asyncio event loop, which adds avoidable overhead in a hot execution path.

→ Testing Review

Status: ✅ Completed
Suggestions: 1 suggestion

The PR changes the MainDriverApi.main invocation path, but there is no regression test covering the new executor-based flow or proving the call no longer runs on the event-loop thread.

Open ZeuZ to inspect full findings, continue an agent conversation, or apply safe patch suggestions.