Function simulateFailedFetch

cli/src/hooks/use-activity-query.ts:632–667

* Simulate the exact retry scheduling logic from doFetch's catch block. * This reproduces the code path that caused the infinite retry loop bug. * Returns whether a retry was scheduled (true) or retries were exhausted (false).

(
    queryKey: readonly unknown[],
    maxRetries: number,
  )

   * Returns whether a retry was scheduled (true) or retries were exhausted (false).
   */
  simulateFailedFetch(
    queryKey: readonly unknown[],
    maxRetries: number,
  ): { retryScheduled: boolean; retryCount: number } {
    const key = serializeQueryKey(queryKey)
    const currentRetries = retryCounts.get(key) ?? 0

    if (currentRetries < maxRetries && (cache.refCounts.get(key) ?? 0) > 0) {
      const next = currentRetries + 1
      retryCounts.set(key, next)

      inFlight.delete(key)
      setQueryFetching(key, false)

      // This is the fixed line — uses clearRetryTimeout instead of clearRetryState
      clearRetryTimeout(key)

      // Don't actually schedule a setTimeout in tests, just record the intent
      return { retryScheduled: true, retryCount: next }
    }

    retryCounts.set(key, 0)

    const existingEntry = getCacheEntry(key)
    setCacheEntry(key, {
      data: existingEntry?.data,
      dataUpdatedAt: existingEntry?.dataUpdatedAt ?? 0,
      error: new Error('Simulated fetch error'),
      errorUpdatedAt: Date.now(),
    })

    inFlight.delete(key)
    setQueryFetching(key, false)

    return { retryScheduled: false, retryCount: 0 }
  },
}