Single channel extension bridge

[cte]

Important

Refactor bridge system to use a single ExtensionChannel, removing TaskChannel and simplifying event handling and task management.

• Bridge System Refactor:
  • Removed TaskChannel and BaseChannel classes, consolidating functionality into ExtensionChannel.
  • Updated BridgeOrchestrator to manage connections and events through ExtensionChannel only.
  • Removed task-specific event handling from BridgeOrchestrator.
• Event Handling:
  • Updated ExtensionChannel to handle all task-related events and commands, including Message, TaskModeSwitched, TaskAskResponded, and more.
  • Refactored event mapping and listener setup in ExtensionChannel.
• Task Management:
  • Removed task subscription logic from Task class in Task.ts.
  • Updated ClineProvider to handle task lifecycle events directly.
• Miscellaneous:
  • Removed TaskChannel tests and related imports.
  • Updated extension.ts to reflect changes in bridge connection management.

^{This description was created by for 86977d2. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Review Summary

Previously identified issues:

• Remove commented-out code block in ExtensionChannel.ts (lines 177-205) - leftover from TaskChannel refactoring

New issues found:

• Fix cleanup flow during manual disconnection - extensionChannel.cleanup() is not called when BridgeOrchestrator.disconnect() is invoked because SocketTransport removes listeners before disconnecting

[roomote]

Review complete. Found 1 minor issue to address before approval.

[roomote]

The cleanup flow is broken during manual disconnection. When BridgeOrchestrator.disconnect() calls socketTransport.disconnect(), the SocketTransport removes all listeners (line 247-248 in SocketTransport.ts) before disconnecting, which prevents the onDisconnect callback from firing. This means extensionChannel.cleanup() is never called during manual disconnection, potentially causing resource leaks. The old code explicitly called cleanup() before disconnect() to avoid this issue.