fix(mothership): clear a dropped run's saved pointer when its hold is released

A reconnect cancelled by navigating away leaves the settled run's execution pointer saved.
Releasing the hold now clears it when it still names that execution, before the next run
is admitted, so recovery cannot later report the finished run as a live one.

Author: waleedlatif1

apps/sim/lib/mothership/tools/client/run-tool-execution.test.ts

@@ -913,6 +913,12 @@ describe('run tool execution cancellation', () => {
         getWorkflowExecution.mockImplementation(() => ({ isExecuting: false }))
       })
 
+      loadExecutionPointer.mockResolvedValue({
+        workflowId: 'wf-1',
+        executionId: 'exec-abandoned',
+        lastEventId: 3,
+      })
+
       executeRunToolOnClient('tool-a', 'run_block', { workflowId: 'wf-1', blockId: 'block-1' })
       executeRunToolOnClient('tool-b', 'run_block', { workflowId: 'wf-1', blockId: 'block-2' })
       await vi.waitFor(() => expect(released).toHaveBeenCalledWith('wf-1'))
@@ -928,6 +934,11 @@ describe('run tool execution cancellation', () => {
 
       reconnect.close()
       await vi.waitFor(() => expect(launchedToolCallIds()).toEqual(['tool-a', 'tool-b']))
+      // The abandoned run's pointer is gone before the next run saves its own.
+      expect(clearExecutionPointer).toHaveBeenCalledWith('wf-1')
+      expect(clearExecutionPointer.mock.invocationCallOrder[0]).toBeLessThan(
+        saveExecutionPointer.mock.invocationCallOrder.at(-1) ?? 0
+      )
       finish('tool-b')
       await drain()
       expect(confirmStatuses()).toEqual([

apps/sim/lib/mothership/tools/client/run-tool-execution.ts

@@ -186,10 +186,17 @@ function releaseRunToolSlot(
   }
 }
 
-function releaseInterruptedHold(workflowId: string, slot: WorkflowRunSlot, executionId: string) {
+async function releaseInterruptedHold(
+  workflowId: string,
+  slot: WorkflowRunSlot,
+  executionId: string
+): Promise<void> {
   if (slot.owner?.kind !== 'interrupted' || slot.owner.executionId !== executionId) return
-  // A reconnect cancelled by navigating away leaves the settled run marked current.
+  // A reconnect cancelled by navigating away leaves the settled run marked current and its
+  // pointer saved; both go before the next run can write its own.
   clearVisibleExecution(workflowId, executionId)
+  const pointer = await loadExecutionPointer(workflowId).catch(() => null)
+  if (pointer?.executionId === executionId) await clearExecutionPointer(workflowId)
   slot.owner = null
   admitNextRunTool(workflowId, slot)
 }
@@ -218,7 +225,7 @@ function watchInterruptedExecution(workflowId: string, slot: WorkflowRunSlot): v
         serverSettled = true
         if (isReconnectStreamOpen(workflowId, executionId)) continue
       }
-      releaseInterruptedHold(workflowId, slot, executionId)
+      await releaseInterruptedHold(workflowId, slot, executionId)
       break
     }
     slot.watchingInterrupted = false