Fix Linear agent hanging on follow-up messages after task completion

[roomote]

Fixes ROO-365: Linear agent hangs when follow-up message is sent after task completion.

Problem

When a Linear agent completes a task with attempt_completion, it shows a completion_result ask and waits for user response. During this waiting period, if Linear sends follow-up messages via the SendMessage IPC command, these messages get queued but are never processed. This causes the agent to hang in a perpetual "thinking" state.

Root Cause

The AttemptCompletionTool was not calling processQueuedMessages() after handling the completion result, unlike other tools (e.g., SearchAndReplaceTool, WriteToFileTool, ApplyDiffTool). This meant that any messages queued while waiting for the completion response would never be processed.

Solution

Added processQueuedMessages() calls in two places within AttemptCompletionTool.execute():

1. After completion is accepted (yesButtonClicked response) - to process any queued messages that arrived during the completion wait
2. After user provides feedback (messageResponse with feedback text) - to process any messages that were queued while the feedback was being handled

This ensures queued follow-up messages are properly dequeued and submitted to the task, preventing the hang.

Testing

• Manually verified the flow with Linear agent sessions
• Existing tests pass (no test regressions)
• Follows the same pattern as other tools that call processQueuedMessages()

---

View task on Roo Code Cloud

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

The changes correctly add processQueuedMessages() calls to AttemptCompletionTool, following the established pattern used by other tools (SearchAndReplaceTool, WriteToFileTool, ApplyDiffTool, etc.). This fix ensures that follow-up messages from Linear/Slack integrations are properly processed after task completion.

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