fix(pi): preserve plan exploration timeout

Author: Bill Leoutsakos

apps/sim/executor/handlers/pi/cloud/plan/backend.test.ts

@@ -105,6 +105,7 @@ describe('runCloudPlanPi', () => {
     expect(piOptions.envs.GITHUB_TOKEN).toBeUndefined()
     expect(piOptions.envs.PI_MODEL).toBe('claude-sonnet-4-6')
     expect(piOptions.envs.PI_THINKING).toBe('high')
+    expect(piOptions.timeoutMs).toBe(30 * 60 * 1000)
 
     expect(mockBuildPrompt).toHaveBeenCalledWith(
       expect.objectContaining({

apps/sim/executor/handlers/pi/cloud/plan/backend.ts

@@ -133,7 +133,7 @@ export const runCloudPlanPi: PiBackendRun<PiCloudPlanRunParams> = async (params,
                   }
                 : {}),
             },
-            timeoutMs: resolvePiTimeoutMs(lifetimeMs),
+            timeoutMs: resolvePiTimeoutMs(lifetimeMs, { finalizePhases: 0 }),
             onStdout: handleChunk,
           }
         ),

apps/sim/executor/handlers/pi/cloud/shared.test.ts

@@ -40,6 +40,13 @@ describe('resolvePiTimeoutMs', () => {
     expect(resolvePiTimeoutMs(shortLifetime)).toBeLessThanOrEqual(shortLifetime)
   })
 
+  it('does not reserve nonexistent finalize phases for Plan', () => {
+    const timeout = resolvePiTimeoutMs(PI_SANDBOX_MAX_LIFETIME_MS, { finalizePhases: 0 })
+
+    expect(timeout).toBeLessThanOrEqual(PI_SANDBOX_MAX_LIFETIME_MS - CLONE_TIMEOUT_MS)
+    expect(timeout).toBeGreaterThan(resolvePiTimeoutMs(PI_SANDBOX_MAX_LIFETIME_MS))
+  })
+
   it('falls back to the single-turn floor when the reserves exhaust the lifetime', () => {
     // A deadline shorter than the bracketing commands' worst case is legitimate
     // (a free-plan sync run). Those ceilings are pessimistic, so leave a short

apps/sim/executor/handlers/pi/cloud/shared.ts

@@ -34,10 +34,10 @@ export const MIN_PI_TIMEOUT_MS = 60 * 1000
  * reaped the sandbox and surface as an opaque SDK error.
  *
  * The reserve matters as much as the cap. The sandbox clock starts at create,
- * and three commands bracket the agent turn: the clone before it, then the
- * commit and the push after it, the last two sharing
- * {@link FINALIZE_TIMEOUT_MS}. Capping at the bare lifetime would mean the
- * sandbox always died first, taking the agent's finished work with it unpushed.
+ * and authoring has three commands around the agent turn: the clone before it,
+ * then the commit and push after it, the last two sharing
+ * {@link FINALIZE_TIMEOUT_MS}. Plan has no finalize phase and sets that reserve
+ * to zero. Capping at the bare lifetime would mean the sandbox died first.
  *
  * Takes the lifetime as an argument rather than reading the provider ceiling
  * itself, because that ceiling is no longer the only lifetime a run can get: a
@@ -53,10 +53,17 @@ export const MIN_PI_TIMEOUT_MS = 60 * 1000
  * through `ttlMinutes`. Reserving the surrounding commands keeps the agent turn
  * inside the lifetime the selected provider actually received.
  */
-export function resolvePiTimeoutMs(lifetimeMs = resolvePiSandboxLifetimeMs()): number {
+export function resolvePiTimeoutMs(
+  lifetimeMs = resolvePiSandboxLifetimeMs(),
+  options?: { finalizePhases?: number }
+): number {
+  const finalizePhases = options?.finalizePhases ?? 2
   return Math.min(
     getMaxExecutionTimeout(),
-    Math.max(lifetimeMs - CLONE_TIMEOUT_MS - 2 * FINALIZE_TIMEOUT_MS, MIN_PI_TIMEOUT_MS)
+    Math.max(
+      lifetimeMs - CLONE_TIMEOUT_MS - finalizePhases * FINALIZE_TIMEOUT_MS,
+      MIN_PI_TIMEOUT_MS
+    )
   )
 }