Fix: Show loading state during initial token fetch to prevent flash

[nicknisi]

Summary

Fixes a race condition that causes a flash of unauthenticated state during initial token fetch.

Problem

useAccessToken was reporting loading: false while fetching the initial token, causing downstream consumers to briefly show unauthenticated state before the token arrived.

This issue necessitated workarounds like checking !accessToken in loading calculations (see workos/template-convex-nextjs-authkit#5), which breaks for logged-out users.

Solution

• Add isInitialTokenLoading state to track initial token fetch
• Report loading: true until the initial fetch completes
• Logged-out users continue to see loading: false as expected

Testing

Updated tests to verify the loading state is shown during initial token fetch.

[Copilot]

Pull Request Overview

This PR fixes a race condition where useAccessToken incorrectly reported loading: false during initial token fetch, causing UI components to briefly flash an unauthenticated state before the token was retrieved.

• Added isInitialTokenLoading state to track when an initial token fetch is in progress
• Modified loading calculation to combine both initial fetch loading and token store loading states
• Updated test cases to verify loading state is properly shown during initial token fetch

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/components/useAccessToken.ts	Implemented initial token loading state tracking and combined loading logic
tests/useAccessToken.spec.tsx	Updated test expectations and added new tests for loading state behavior

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}