Import AITURK IDE 1.0.0-beta.1 from Hermes 63279301; preserve MIT license

apps/desktop/vitest.setup.ts

@@ -0,0 +1,46 @@
+import { configure } from '@testing-library/react'
+
+// Node 26 defines its own `localStorage` accessor on the global object, which
+// returns `undefined` unless the process was started with --localstorage-file
+// (it warns: "localStorage is not available because --localstorage-file was
+// not provided"). In the jsdom environment `globalThis` IS the window, so that
+// accessor shadows jsdom's Storage and every `localStorage.getItem(...)` in a
+// test throws "Cannot read properties of undefined". Install a real in-memory
+// Storage when the global resolves to nothing, before any test module reads it.
+if (typeof (globalThis as any).localStorage === 'undefined') {
+  const store = new Map<string, string>()
+  const storage: Storage = {
+    get length() {
+      return store.size
+    },
+    key: (i: number) => [...store.keys()][i] ?? null,
+    getItem: (k: string) => store.get(String(k)) ?? null,
+    setItem: (k: string, v: string) => void store.set(String(k), String(v)),
+    removeItem: (k: string) => void store.delete(String(k)),
+    clear: () => store.clear(),
+  }
+  for (const target of [globalThis, (globalThis as any).window].filter(Boolean)) {
+    Object.defineProperty(target, 'localStorage', {
+      value: storage,
+      configurable: true,
+      writable: true,
+    })
+  }
+}
+
+// React 19 + Testing Library 16: opt into the act environment so render(),
+// fireEvent(), and findBy* queries automatically flush state updates without
+// spurious "not wrapped in act(...)" warnings.
+;(globalThis as any).IS_REACT_ACT_ENVIRONMENT = true
+
+// findBy*/waitFor default to a 1000ms deadline — too tight for async-heavy
+// panels (radix menus, refetch chains) when the full suite runs under xdist
+// CPU contention in CI. Success still resolves the instant the node appears;
+// the wider deadline only absorbs a starved runner, killing timing flakes.
+// 5s proved insufficient on saturated runners (2026-08-31: gateway-settings,
+// messaging, session-unread-tile, toolset-config-panel each tripped a
+// waitFor(mock-called) deadline on runs whose only common factor was load —
+// including a plugins-only commit on main). 12s mirrors the same reasoning
+// as the 15s testTimeout above it while still finishing below it, so a
+// genuinely hung await still surfaces as this assertion, not a test timeout.
+configure({ asyncUtilTimeout: 12_000 })