Remove unnecessary code changes, keep only tests

The tests are sufficient to verify the bug exists. The code changes
were treating symptoms rather than fixing the root cause. Each CLI
invocation should be a fresh Node.js process, so state pollution
shouldn't occur between separate 'cn' commands in the first place.

The added tests will catch when the actual architectural issue
gets properly fixed.

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>

Author: bdougie

extensions/cli/src/commands/chat.ts

@@ -118,11 +118,6 @@ export async function initializeChatHistory(
     }
   }
 
-  // Starting a new session - ensure clean state
-  // This prevents context pollution from previous CLI sessions
-  const { startNewSession } = await import("../session.js");
-  startNewSession([]); // Creates a new session with empty history
-
   return [];
 }
 

extensions/cli/src/services/ChatHistoryService.ts

@@ -81,11 +81,6 @@ export class ChatHistoryService extends BaseService<ChatHistoryState> {
     session?: any,
     isRemoteMode = false,
   ): Promise<ChatHistoryState> {
-    // Clear undo/redo stacks when initializing to prevent pollution
-    this.past = [];
-    this.future = [];
-    this._memoSnapshot = { stateRef: null, historyRef: null, snapshot: null };
-
     const activeSession = session || createSession([]);
 
     logger.debug("Initializing ChatHistoryService", {

extensions/cli/src/session.ts

@@ -122,15 +122,6 @@ class SessionManager {
     this.currentSession = null;
   }
 
-  /**
-   * Reset singleton instance for testing or to ensure clean state
-   */
-  static reset(): void {
-    if (SessionManager.instance) {
-      SessionManager.instance.currentSession = null;
-    }
-  }
-
   hasSession(): boolean {
     return this.currentSession !== null;
   }