Suppress connection error stack traces in client executables

Rescue connection errors (e.g. ConnectionResetError) inside the Async
block to prevent Async's "unhandled exception" warning, and output
clean error messages to stderr. Full backtraces are available via
TERMINALWIRE_DEBUG=1.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: bradgessler

gem/terminalwire-client/lib/terminalwire/client.rb

@@ -39,6 +39,10 @@ def self.websocket(url:, arguments: ARGV, &configuration)
           adapter = Terminalwire::Adapter::Socket.new(transport)
           Terminalwire::Client::Handler.new(adapter, arguments:, endpoint:, &configuration).connect
         end
+      rescue Terminalwire::Error
+        raise
+      rescue => e
+        raise Terminalwire::Error, "Connection failed: #{e.message}"
       end
     end
   end

gem/terminalwire/exe/terminalwire

@@ -4,6 +4,7 @@ require "terminalwire/client"
 begin
   Terminalwire::Client.websocket(url: "wss://terminalwire.com/terminal")
 rescue Terminalwire::Error => e
-  puts e.message
+  $stderr.puts e.message
+  $stderr.puts e.cause.full_message if ENV["TERMINALWIRE_DEBUG"] && e.cause
   exit 1
 end

gem/terminalwire/exe/terminalwire-exec

@@ -8,6 +8,7 @@ begin
 rescue Interrupt
   exit 0
 rescue Terminalwire::Error => e
-  puts e.message
+  $stderr.puts e.message
+  $stderr.puts e.cause.full_message if ENV["TERMINALWIRE_DEBUG"] && e.cause
   exit 1
 end