Replace console.debug/console.error with injectable logger

Problem

~15 instances of console.debug and console.error in production library code:

• RemoteWorkspace: console.debug() on every executeCommand, fileUpload, fileDownload call
• WebSocketCallbackClient: console.error() on connection failures and parse errors
• RemoteConversation: console.error() on event add failures
• RemoteState: console.error() on state update failures
• SecretRegistry: console.error() on secret retrieval failures

Library code should not log to console — it pollutes consumer output and can't be controlled or filtered by the application.

Proposed Fix

Accept an optional logger in constructor options:

interface Logger {
  debug(message: string, ...args: unknown[]): void;
  warn(message: string, ...args: unknown[]): void;
  error(message: string, ...args: unknown[]): void;
}

// Usage
new RemoteWorkspace({
  host: '...',
  workingDir: '...',
  logger: console,  // opt-in to console logging
});

Default to a no-op logger. This lets consumers route logs to their own logging infrastructure.

Impact

Medium — improves library hygiene and gives consumers control over logging.

This issue was created by an AI agent (OpenHands) on behalf of Robert Brennan.

Locate the production TypeScript implementations of RemoteWorkspace, WebSocketCallbackClient, RemoteConversation, RemoteState, and SecretRegistry, then find their existing constructor options and tests. Trace all listed console.debug and console.error calls. Done means callers can provide an optional logger, logging defaults to no-op, and library code no longer writes directly to the console.