fix(cli): keep a sub-millisecond timeout bounded

Zero is how this function says "no bound", so rounding a positive
SIM_TIMEOUT_SECONDS down to zero inverted the request: anything under
0.0005s asked for the shortest possible timeout and got none at all, leaving
a stalled request to hang. Introduced by the rounding that fixed the
fractional-millisecond rejection.

Floored at 1ms for every positive value; only a literal 0 still disables.

Author: waleedlatif1

packages/sim-cli/src/http/client.test.ts

@@ -378,6 +378,22 @@ describe('a request that never answers', () => {
     await expect(client().request('/api/v2/workflows')).resolves.toBeDefined()
   })
 
+  it('keeps a bound below half a millisecond bounded, rather than disabling it', async () => {
+    // Zero means "no bound", so rounding a positive value down to zero inverted
+    // the request: the shortest timeout anyone could ask for became none.
+    vi.stubEnv('SIM_TIMEOUT_SECONDS', '0.0004')
+    const fetchMock = vi.fn().mockResolvedValue(
+      new Response(JSON.stringify({ data: [] }), {
+        status: 200,
+        headers: { 'content-type': 'application/json' },
+      })
+    )
+    vi.stubGlobal('fetch', fetchMock)
+
+    await client().request('/api/v2/workflows')
+    expect(fetchMock.mock.calls[0][1].signal).toBeInstanceOf(AbortSignal)
+  })
+
   it('refuses a delay longer than Node can wait, which would silently become 1ms', async () => {
     // Past 2^31-1 ms Node does not fail — it clamps to 1ms, so the request the
     // caller asked to wait longest for would be the first one aborted.

packages/sim-cli/src/http/client.ts

@@ -300,8 +300,10 @@ function resolveTimeoutMs(env: NodeJS.ProcessEnv = process.env): number {
 
   // Rounded because a fractional millisecond is rejected outright by
   // `AbortSignal.timeout`, and a sub-millisecond timeout is not a distinction
-  // anyone is drawing.
-  const ms = Math.round(seconds * 1000)
+  // anyone is drawing. Floored at 1ms for anything above zero: rounding alone
+  // sent a bound under 0.0005s to 0, which this function reserves for "no
+  // bound at all", so asking for the shortest possible timeout produced none.
+  const ms = seconds === 0 ? 0 : Math.max(1, Math.round(seconds * 1000))
   if (ms > MAX_TIMEOUT_MS) {
     throw new SimApiError(
       `SIM_TIMEOUT_SECONDS "${raw}" is longer than Node can wait (${Math.floor(MAX_TIMEOUT_MS / 1000)}s). Use 0 to wait indefinitely.`,