Settings sign-in flow fails to reflect authenticated state

[rosscado]

After completing the SayPi login/OAuth flow, the extension settings page remains in an unauthenticated state until the user manually reloads the tab. This creates confusion and makes the sign-in experience feel unreliable.

Steps to reproduce:

1. Open Claude (or any supported chatbot) and launch the SayPi extension settings via the embedded “Voice settings” entry point or the toolbar action button.
2. In the settings page, click “Sign In”.
3. Complete authentication at https://www.saypi.ai/auth/login (Google/GitHub/magic link).
4. When the login tab closes and focus returns to the settings tab, observe the UI.

Expected result:

• The settings view immediately shows a signed-in state (user name, quotas, “Sign Out” button) with a clear confirmation that authentication succeeded.

Actual result:

• The settings page still displays the unauthenticated UI (“Not signed in”, “Sign In” button). The user must manually refresh the tab to see the signed-in experience.

Environment:

• SayPi extension v1.10.3 (Manifest V3)
• Reproduced on Chrome 130, Edge 128, Arc 1.50, Firefox 130 (desktop), Firefox Mobile 129
• Occurs regardless of SSO provider

Additional notes:

• Background service worker successfully refreshes the JWT (verified via logs).
• Settings page does not receive or react to the updated auth state.
• Users perceive the flow as “broken” and may retry sign-in or abandon the process.

[rosscado]

PRD added to scripts/ directory outlining a proposed solution.
SayPi Extension Authentication Flow PRD.pdf