fix: process queued messages immediately after any tool completion

[roomote]

This PR attempts to address Issue #9315. Feedback and guidance are welcome.

Problem

Queued messages were not being reliably injected into chat conversations. They were waiting for approval-related actions instead of being processed ASAP.

Solution

Added processQueuedMessages() call to the central pushToolResult function in presentAssistantMessage.ts. This ensures queued messages are processed immediately after ANY tool completion.

Changes

• Modified presentAssistantMessage.ts to call processQueuedMessages() in pushToolResult
• Removed redundant calls from individual tool files

Fixes #9315

---

Important

This PR modifies presentAssistantMessage.ts to process queued messages immediately after tool completion, removing redundant calls from individual tool files.

• Behavior:
  • Calls processQueuedMessages() in pushToolResult in presentAssistantMessage.ts to process queued messages immediately after any tool completion.
  • Removes redundant processQueuedMessages() calls from ApplyDiffTool.ts, InsertContentTool.ts, MultiApplyDiffTool.ts, and WriteToFileTool.ts.
• Files:
  • presentAssistantMessage.ts: Modified to include processQueuedMessages() call.
  • ApplyDiffTool.ts, InsertContentTool.ts, MultiApplyDiffTool.ts, WriteToFileTool.ts: Redundant calls removed.

^{This description was created by for bbd8f78. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

The PR successfully addresses the queued messages issue by centralizing the processQueuedMessages() call in the pushToolResult function. This ensures queued messages are processed immediately after ANY tool completion, rather than waiting for approval-related actions.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}