feat(cloud): Add telemetry retry queue for network resilience

[daniel-lxs]

Summary

Implements a retry queue for cloud telemetry events to prevent data loss during network failures.

Changes

• Add RetryQueue class with workspace-scoped persistence
• Queue failed telemetry events for automatic retry
• Retry events every 60 seconds with fresh auth tokens
• FIFO eviction when queue reaches 100 events
• Persist queue across VS Code restarts

Implementation Details

• RetryQueue: Manages failed requests with persistence and automatic retry logic
• CloudTelemetryClient: Integrates retry queue to catch network errors
• CloudService: Initializes retry queue with auth header provider

Testing

• All existing tests pass (229 tests)
• Added 8 new tests for RetryQueue functionality
• TypeScript compilation successful

Context

This feature was migrated from RooCodeInc/Roo-Code-Cloud#744 to ensure telemetry data isn't lost during network failures or temporary server issues.

The retry queue activates when telemetry events fail due to network errors. Events are retried until successful or evicted by newer events.

---

Important

Introduces RetryQueue for retrying failed telemetry events in CloudTelemetryClient, with persistence and auth state handling.

• Behavior:
  • Introduces RetryQueue to handle failed telemetry events in CloudTelemetryClient.
  • Retries events every 60 seconds with fresh auth tokens.
  • Supports FIFO eviction when queue reaches 100 events.
  • Persists queue across VS Code restarts.
  • Handles network errors, server errors (5xx), and rate limiting (429).
  • Does not retry on client errors (4xx) except 429.
• Integration:
  • CloudService initializes RetryQueue with auth header provider.
  • CloudTelemetryClient uses RetryQueue to queue failed requests.
• Testing:
  • Adds 8 new tests for RetryQueue functionality.
  • Ensures queue handles auth state changes, network errors, and rate limits.
• Misc:
  • Exports RetryQueue and related types in index.ts.

^{This description was created by for f4242ca. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for implementing the telemetry retry queue! This is a valuable feature for network resilience. I've reviewed the changes and have some feedback:

Critical Issues (Must Fix):

1. Unusual retry order logic - The retryAll() method in RetryQueue.ts processes the newest request first, then switches to oldest-first for remaining requests. This could lead to unpredictable retry behavior. Consider using consistent FIFO order.

2. Missing error detection for retry-worthy failures - The retry queue only activates for TypeError with "fetch failed" message in TelemetryClient.ts. This misses other network errors like timeouts, DNS failures, or connection resets.

Important Suggestions (Should Consider):

3. Potential memory leak with FormData - The backfillMessages method creates FormData with potentially large message arrays, but the retry mechanism might not handle multipart/form-data correctly when serialized.

4. Missing retry limit enforcement - The maxRetries config is defined but never used. Failed requests could retry indefinitely.

5. Race condition in retryAll() - The isProcessing flag prevents concurrent retry attempts, but multiple timer triggers could be lost.

Minor Improvements:

6. Missing tests for retry logic - Tests verify queueing and persistence but don't test the actual retryAll() method.

7. Hardcoded timeout value - The 30-second timeout in retryRequest should be configurable.

8. No exponential backoff - Consider implementing exponential backoff to reduce server load during outages.

[ellipsis-dev]

handleAuthStateChangeForRetryQueue cleanly manages pausing, clearing, and resuming the retry queue on different auth states. Consider refactoring the duplicate resume() calls (lines 417–424) for clarity.

[ellipsis-dev]

In the 429 rate limiting branch, the code sets a global pause using the Retry-After header if present. Consider applying a default pause delay if the header is missing to avoid immediate reprocessing.