Raise test timeouts across the spawn-heavy suite for Windows CI

terminal-manager.test.ts hit the same class of failure as the
resource-monitor fix: a spawn-and-poll test's local waitFor() default
(5000ms) coincided with vitest's outer 5000ms default, so a slow PTY
spawn on Windows CI runners tripped the outer timeout before the
helper's own error could fire. Rather than patch each spawn-heavy
file as CI surfaces the next one, set a 20s testTimeout globally in
vitest.config.ts and raise the local waitFor() defaults in
terminal-manager.test.ts and agent-tools.test.ts (both hit the same
pattern) to 12s, giving genuine headroom instead of just a longer
outer ceiling around an already-too-tight inner one.

Author: voidstackloop

app/src/agent-tools.test.ts

@@ -38,7 +38,10 @@ import {
     applyPatch,
 } from "./agent-tools";
 
-function waitFor(predicate: () => boolean, timeoutMs = 5000): Promise<void> {
+// 5000ms was tight enough that a slow spawn on Windows CI could still hit
+// vitest's outer testTimeout (see app/vitest.config.ts) before this helper's
+// own, more descriptive error had a chance to fire.
+function waitFor(predicate: () => boolean, timeoutMs = 12_000): Promise<void> {
     const start = Date.now();
     return new Promise((resolve, reject) => {
         const check = () => {
@@ -487,7 +490,7 @@ describe("agent-tools", () => {
             closeAllTerminals();
         });
 
-        function waitFor(predicate: () => boolean | Promise<boolean>, timeoutMs = 5000): Promise<void> {
+        function waitFor(predicate: () => boolean | Promise<boolean>, timeoutMs = 12_000): Promise<void> {
             const start = Date.now();
             return new Promise((resolve, reject) => {
                 const check = async () => {

app/src/terminal-manager.test.ts

@@ -13,7 +13,10 @@ import {
     listTerminals,
 } from "./terminal-manager";
 
-function waitFor(predicate: () => boolean, timeoutMs = 5000): Promise<void> {
+// 5000ms was tight enough that a slow PTY spawn on Windows CI could still
+// hit vitest's outer testTimeout (see app/vitest.config.ts) before this
+// helper's own, more descriptive error had a chance to fire.
+function waitFor(predicate: () => boolean, timeoutMs = 12_000): Promise<void> {
     const start = Date.now();
     return new Promise((resolve, reject) => {
         const check = () => {

app/vitest.config.ts

@@ -10,5 +10,13 @@ export default defineConfig({
     test: {
         environment: "node",
         include: ["src/**/*.test.ts"],
+        // Several tests spawn a real child process or PTY and poll for
+        // observable output (agent-tools.test.ts, resource-monitor.test.ts,
+        // terminal-manager.test.ts). Vitest's 5000ms default has repeatedly
+        // been too tight for that on Windows CI runners, where process/PTY
+        // spawn is noticeably slower than on Linux/macOS — this raises the
+        // floor for the whole suite instead of chasing each Windows-only
+        // flake one file at a time as it turns up.
+        testTimeout: 20_000,
     },
 });