fix(livekit): use asyncio.to_thread so status-update task actually runs

[devteamaegis]

Problem

The LiveKit tool handler is intended to display a status message to the user
while the underlying AgentMail API call is in flight:

status_update_task = asyncio.create_task(_status_update())

result = tool.func(self.client, raw_arguments).model_dump_json()  # sync HTTP

status_update_task.cancel()

tool.func calls the synchronous AgentMail client, which uses httpx.Client
and blocks the calling thread. In an async context that means the event
loop is blocked for the entire duration of the HTTP request. Because the
event loop cannot run other tasks while it is blocked, _status_update is
never scheduled. When tool.func finally returns, the very next line cancels
the task — so generate_reply is never called and the user never sees the
status update.

Fix

Off-load tool.func to a thread pool with asyncio.to_thread. The event
loop stays free while the HTTP call runs in a worker thread, giving
_status_update the time slice it needs to run:

# before
result = tool.func(self.client, raw_arguments).model_dump_json()

# after
result = await asyncio.to_thread(
    lambda: tool.func(self.client, raw_arguments).model_dump_json()
)

Tests

python/tests/test_livekit_status_update.py (both pass):

• test_status_update_fires_during_blocking_tool — a slow sync tool is used; after releasing the gate the test verifies generate_reply was called
• test_tool_result_returned_correctly — the JSON result is still returned correctly after the change

---

Summary by cubic

Prevents the LiveKit tool handler from blocking the event loop by running the synchronous AgentMail HTTP call in a thread. This allows the status-update task to run so users see progress while the tool executes.

• Bug Fixes
  • Off-load tool.func(...).model_dump_json() via asyncio.to_thread so _status_update can run and call generate_reply.
  • Add tests to confirm the status update fires during a slow sync tool and the JSON result is still returned correctly.

^{Written for commit 318509e. Summary will update on new commits. Review in cubic}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}