Fix TerminalProcess output parsing

[KJ7LNW]

This PR from cline could benefit Roo-Cline, but it does not yet merge cleanly. I am not familiar with Roo's changes so please review and see if it would be a good fit.

• Fix TerminalProcess output parsing cline/cline#1089

This drastically increases the command line output reliability. It also works around VSCode bug microsoft/vscode#237208

You can see as follows by providing these instructions:

use execute_command for simple commands like echo a repeatedly until you have exhausted all test permutations. display the execute command syntax immediately upon my response of content. report the exit code. i will provide you with the exit code in my response do not display the exit code or the signal type in any part I am snippet that you are write. do not chain commands each command should be single. test exit codes using one line Perl commands to print and kill the program itself. exit code above 127 are invalid. run multiple tests and notify me of any unexpected conditions where are the output you receive is not the output that you expect. try edge cases but exclude shell special characters like !. include tests that may generate core dumps. provide a summary in markdown format and save it to doc.md. test differences between /bin/echo and echo shell built-in. also test echo -n. makes sure all program tests exit (no infinite loops). test multiple signals in the kill testing. elaborate on what was unexpected. format the response in markdown using markdown bullets where headings are bullets. if there are problems elaborates with details. nothing command output is trimmed at the beginning and end of white space. use bullets as headings.

Providing instruction above to Cline produces results like the following:

With fixes from that PR

Command Testing Results

• Echo Command Tests

  • Built-in echo vs /bin/echo comparison
    • Both produced identical output for basic text
    • Both handled -n flag identically
    • Whitespace handling showed trimming behavior in shell

• Exit Code Tests

  • Normal exit codes (0-1)
    • exit(0) produced expected success
    • exit(1) produced expected error state

• Signal Tests

  • SIGKILL (9)
    • Process terminated as expected
    • "Killed" message displayed
  • SIGTERM (15)
    • Process terminated as expected
    • "Terminated" message displayed
  • SIGSEGV (11)
    • Successfully triggered segmentation fault
    • Core dump was generated as expected
    • "Segmentation fault (core dumped)" message displayed

• Whitespace Handling

  • Echo command appears to trim whitespace
  • Both leading and trailing spaces were removed
  • This behavior was consistent across both built-in and binary echo

• Unexpected Behaviors

  • None observed - all commands behaved according to POSIX specifications
  • Signal handling produced expected messages
  • Exit codes were within valid range (0-127)
  • Core dump generation worked as expected

• Test Environment

  • Linux system
  • Bash shell
  • All commands executed successfully
  • No infinite loops or hanging processes observed

Current Cline with terminal problems

• Command Testing Results

• Echo Command Analysis

  • echo hello

    • Expected: Simple "hello" output
    • Actual: Additional control sequence ";preexec" and shell prompt included
    • Unexpected: Terminal metadata injection in output stream

  • /bin/echo hello

    • Expected: Identical output to shell builtin
    • Actual: Command echo and UUID sequence "7ceb487c-072e-4cd7-bce9-5bac16261f0f" injected
    • Unexpected: Different output formatting than shell builtin

  • echo -n hello

    • Expected: "hello" without newline
    • Actual: Command echo and control sequences present
    • Unexpected: Control sequences still visible despite -n flag

• Exit Code Testing

  • perl -e 'exit(0)'

    • Expected: Silent exit
    • Actual: Command echo and completion notification included
    • Unexpected: Terminal metadata visible in success case

  • perl -e 'exit(1)'

    • Expected: Silent error exit
    • Actual: Only completion notification shown
    • Unexpected: Different output pattern than exit(0)

  • perl -e 'exit(255)'

    • Expected: Silent max exit code
    • Actual: Only completion notification shown
    • Unexpected: Identical output to exit(1) despite different exit code

• Signal Handling Analysis

  • perl -e 'kill TERM, $$'

    • Expected: Process termination message
    • Actual: Command echo, UUID, "Terminated" message
    • Unexpected: UUID injection in signal output

  • perl -e 'kill INT, $$'

    • Expected: Process interrupt message
    • Actual: Only completion notification
    • Unexpected: No visible interrupt message unlike TERM

  • perl -e 'kill SEGV, $$'

    • Expected: Crash with core dump
    • Actual: Command echo, UUID, "Segmentation fault (core dumped)"
    • Unexpected: Core dump message but clean terminal exit

• Terminal Behavior Patterns

  • Control sequences consistently injected in command output
  • UUID sequences appear in specific command outputs
  • Signal handling produces inconsistent output formatting
  • Shell completion notifications vary between exit types
  • Terminal metadata leaks into visible output stream