fix: auto-continue command execution when auto-approved

[JohnBurtt10-bot]

Summary

• Fixes command execution not continuing when command_output ask is auto-approved
• Previously, process.continue() was only called when response was messageResponse, but auto-approval returns yesButtonClicked
• Now process.continue() is called for any response type, ensuring auto-approved commands continue properly

Test plan

1. Enable auto-approval for commands
2. Run a long-running command (e.g., npm run dev)
3. Verify the "Continue While Running" prompt auto-continues without user interaction

---

Important

Fixes auto-approved command execution in ExecuteCommandTool.ts by ensuring process.continue() is called for all response types.

• Behavior:
  • Fixes issue in executeCommandInTerminal() in ExecuteCommandTool.ts where auto-approved commands did not continue execution.
  • Ensures process.continue() is called for any response type, including yesButtonClicked and messageResponse.
• Testing:
  • Verified by enabling auto-approval and running a long command to check auto-continue functionality.

^{This description was created by for a281918. 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 fix correctly addresses the bug where process.continue() was only called for messageResponse but not for yesButtonClicked (auto-approval). Since command_output is a non-blocking ask that gets auto-approved, moving process.continue() outside the conditional ensures commands continue properly.

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