docs: document CTE state parity and backward compatibility

Author: yogeshchoudhary147

EXAMPLES.md

@@ -152,6 +152,7 @@ export default TokenExchange;
 - The external token must be validated in Auth0 Actions using strong cryptographic verification
 - This method implements RFC 8693 token exchange grant type
 - The audience and scope can be provided directly in the options or will fall back to SDK defaults
+- **State Management:** This method triggers the `GET_ACCESS_TOKEN_COMPLETE` action internally upon completion. This ensures that the SDK's `isLoading` and `isAuthenticated` states behave identically to the standard `getAccessTokenSilently` flow.
 
 ## Protecting a route in a `react-router-dom v6` app
 

src/auth0-provider.tsx

@@ -289,6 +289,10 @@ const Auth0Provider = <TUser extends User = User>(opts: Auth0ProviderOptions<TUs
       } catch (error) {
         throw tokenError(error);
       } finally {
+        // We dispatch the standard GET_ACCESS_TOKEN_COMPLETE action here to maintain 
+        // backward compatibility and consistency with the getAccessTokenSilently flow. 
+        // This ensures the SDK's internal state lifecycle (loading/user updates) remains 
+        // identical regardless of whether the token was retrieved via silent auth or CTE.
         dispatch({
           type: 'GET_ACCESS_TOKEN_COMPLETE',
           user: await client.getUser(),