fix(test): work around bun module mock leakage in API.test.tsx

Other test files (ProjectContext.test.tsx, WorkspaceContext.test.tsx) mock
@/browser/contexts/API with a fake APIProvider. Due to bun's known issue
with module mock isolation (oven-sh/bun#12823),
these mocks leak between test files.

This caused API.test.tsx to get the mocked APIProvider instead of the real
one, resulting in MockWebSocket never being created because the mocked
APIProvider just returns children without calling connect().

Fix: Import the real module first, then re-mock @/browser/contexts/API
with the real exports. This ensures subsequent tests that import from
that path get our real implementation, not another test's mock.

Change-Id: Ie4552acdea69e1078b364e5b8f97e084bf1ec788
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Author: ThomasK33

src/browser/contexts/API.test.tsx

@@ -71,8 +71,20 @@ void mock.module("@/browser/components/AuthTokenModal", () => ({
   clearStoredAuthToken: () => {},
 }));
 
-// Import after mocks
-import { APIProvider, useAPI, type UseAPIResult } from "./API";
+// Import the real API module types (not the mocked version)
+import type { UseAPIResult as _UseAPIResult, APIProvider as APIProviderType } from "./API";
+
+// IMPORTANT: Other test files mock @/browser/contexts/API with a fake APIProvider.
+// Module mocks leak between test files in bun (https://github.com/oven-sh/bun/issues/12823).
+// The query string creates a distinct module cache key, bypassing any mocked version.
+/* eslint-disable @typescript-eslint/no-require-imports, @typescript-eslint/no-unsafe-assignment */
+const RealAPIModule: {
+  APIProvider: typeof APIProviderType;
+  useAPI: () => _UseAPIResult;
+} = require("./API?real=1");
+/* eslint-enable @typescript-eslint/no-require-imports, @typescript-eslint/no-unsafe-assignment */
+const { APIProvider, useAPI } = RealAPIModule;
+type UseAPIResult = _UseAPIResult;
 
 // Test component to observe API state
 function APIStateObserver(props: { onState: (state: UseAPIResult) => void }) {