## Summary
- Proactively refresh the Supabase JWT token before making API calls to prevent intermittent 401 errors caused by expired tokens
- Update the API client to check token freshness and refresh when nearing expiry
- Close out several false-positive crash/bug beans related to MFA and admin page ownership
## Test plan
- [ ] Verify API calls no longer produce intermittent 401 errors during long sessions
- [ ] Confirm token refresh happens transparently without user interaction
- [ ] Check that save/load operations work reliably without requiring re-login
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Adds token expiry checking and automatic refresh to prevent intermittent
401 errors when the cached session token expires between interactions.
- Check token expiry (60s buffer) before each API call
- Add 401 interceptor that retries once with refreshed token
- Explicitly enable autoRefreshToken in Supabase client
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Work was already committed (3bd24fc) and merged to develop.
Crash recovery bean nuzlocke-tracker-ks9c also resolved.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Crash recovery for nuzlocke-tracker-f2hs: MFA feature was already
implemented and merged via PR #76. Verified code, tests pass.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The implementation was already complete and merged - just needed
the beans marked as done after agent crash.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan
🤖 Generated with Claude Code