From ac8cd2abe16f9b139e192b844bf4b8a955dfed22 Mon Sep 17 00:00:00 2001
From: garrytan <garrytan@gmail.com>
Date: Thu, 29 Oct 2026 17:18:03 +0000
Subject: [PATCH] test(ship-budget): give the GSTA-152 PR B replay an explicit
 120s timeout

It spawns about 100 CLI processes; on windows-latest it ran past the
shard runner's 30s per-test timeout (windows-free-shard 5, run
40917695070), and on 2 cores it sat at bare bun test's 5s default.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---
 test/ship-budget-projection.test.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/ship-budget-projection.test.ts b/test/ship-budget-projection.test.ts
index 21df72684..a0fd46ad8 100644
--- a/test/ship-budget-projection.test.ts
+++ b/test/ship-budget-projection.test.ts
@@ -113,7 +113,7 @@ describe('projection calibrated from the run\'s own meter (GST-101)', () => {
     }
     expect(stop).toContain('STOP: reason=budget_exhausted');
     expect(reading + STOP_26).toBeLessThanOrEqual(cap);
-  });
+  }, 120_000);
 
   test('the prior holds until the first measurement; the tail reserve scales with the measured step cost', () => {
     const h = fresh();