- Update ConnectionStatus type: replace 'initializing' with 'connecting'
- Create useRetry hook with exponential backoff logic
- Add comprehensive tests for useRetry hook
- Export useRetry from hooks index

Implements:
- Initial delay: 1 second
- Max delay: 30 seconds
- Backoff multiplier: 2
- Max retry attempts: 10

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Fix startRetrying to immediately perform first retry
- Adjust retry scheduling conditions
- Fix delay calculation for exponential backoff

Still debugging test failures

- Fix attemptCount to represent attempts started, not completed
- Fix exponential backoff delay calculation
- Fix retry scheduling conditions for proper max attempts handling
- All 10 useRetry tests now pass
- No regressions in existing test suite

Implements correct behavior:
- attemptCount increments when retry starts
- Exponential backoff: 1s, 2s, 4s, 8s, 16s, 30s (capped)
- Respects maxAttempts limit
- Manual retry cancels automatic retries
- State resets properly on success

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Add parentheses around arrow function parameter
- Fix indentation

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Replace setTimeout/setInterval with window.setTimeout/window.setInterval
- Replace clearTimeout/clearInterval with window.clearTimeout/window.clearInterval
- Fixes TypeScript error: Type 'Timeout' is not assignable to type 'number'
- Ensures proper browser environment timer types

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

Convert useRetry hook from multiple useState calls to a single useReducer
for cleaner state management. This improves code clarity and makes state
transitions more predictable.

Changes:
- Replace 5 useState calls with single useReducer
- Add RetryState interface and RetryAction union type
- Implement retryReducer function for all state transitions
- Update all state access to use state object
- Replace setState calls with dispatch calls throughout

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Created useWithRetry hook with simple interface (call, retryAt, isLoading)
- Implements exponential backoff with configurable options
- Includes comprehensive tests covering all scenarios
- Added usage examples for different configurations
- Follows existing code patterns and uses constants for configuration

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Remove example file as requested
- Fix circular dependency issue using useRef pattern
- Ensure proper cleanup and timer management
- Implementation follows existing codebase patterns

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Remove useRetry.ts and useRetry.test.ts files
- Update hooks index.ts to remove useRetry export
- useWithRetry provides simpler interface for retry functionality

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Remove options parameter - hook now uses fixed configuration
- Update max attempts to 10 (from 3)
- Update max delay to 10 minutes (from 8 seconds)
- Remove countdown logic - no interval ref needed
- Consolidate state into single RetryState object
- Calculate delay inline where it's used
- Remove separate executeFunction - logic moved into call function
- Only use functions for reusable logic (clearTimer)
- Update tests to match new implementation
- Run formatting and linting checks

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

- Do not reset attemptCount when no more attempts are possible
- Add attemptCount to UseWithRetryResult interface
- Return attemptCount in hook result for tracking
- Update tests to verify attemptCount preservation
- Add comprehensive test for attemptCount behavior

This allows consumers to track how many attempts were made,
even after all retry attempts have been exhausted.

Co-authored-by: BrunoQuaresma <3165839+BrunoQuaresma@users.noreply.github.com>

Remove the MAX_ATTEMPTS constant and associated logic to allow unlimited
retry attempts. The hook now retries indefinitely with exponential backoff
(capped at 10 minutes delay) until the operation succeeds or is cancelled.

Update tests to verify the new unlimited retry behavior while maintaining
all existing functionality like cancellation, cleanup, and proper state
management.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

…me retryAt to nextRetryAt

- Remove attemptCount from RetryState interface as it's not needed externally
- Rename retryAt to nextRetryAt for better clarity
- Simplify all setState calls to only manage isLoading and nextRetryAt
- Keep attempt tracking local to executeAttempt function for delay calculation

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

…EffectEvent

- Update all test references from retryAt to nextRetryAt to match the new API
- Add useEffectEvent import to stabilize function reference and prevent unnecessary re-renders
- Update callback dependency from fn to stableFn for better performance
- All tests now pass with the updated API

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Add mountedRef to track component mount state and prevent:
- setState calls after component unmount
- Scheduling new retry timeouts when async operations complete after unmount

This fixes a memory leak where in-flight async operations could schedule
new retries even after the component was unmounted.

Changes:
- Add mountedRef.current checks before all setState calls
- Add mountedRef.current checks before scheduling timeouts
- Set mountedRef.current = false in cleanup
- Add test to verify fix prevents retries after unmount

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

- Change call() return type from Promise<void> to void
- Add guard to prevent multiple concurrent calls when isLoading is true
- Add test case to verify no duplicate calls during loading state
- Update executeAttempt to use default parameter instead of explicit 0

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>