Auto-retry the original mutation after re-authenticating from the SIWE 401 banner

[Lakes41]

Difficulty: Intermediate
Type: bug

Background
The README documents that "401 from backend shows inline re-auth banner without page redirect" as step 8 of the SIWE sign-in flow, implying admins can re-authenticate in place after a session expires.

Problem
After an admin re-authenticates via the inline banner, the mutation that originally triggered the 401 (e.g., a role assignment or policy update) is likely lost, forcing the admin to manually redo the action instead of it completing automatically once a valid session is restored.

Expected outcome
When a mutation fails with 401 (via AuthError from lib/api/live.ts), the UI shows the re-auth banner, and upon successful re-authentication, the original mutation is automatically retried with the new token — with a clear success/failure toast either way.

Suggested implementation

• Extend the AuthError handling path in lib/api/live.ts (or the calling hook) to capture the failed request's parameters before surfacing the re-auth banner.
• After useSiweAuth() completes a successful re-auth, replay the captured request using the new token.
• Ensure only one retry attempt occurs (avoid infinite loops if the retried request also 401s).
• Add a toast/notification confirming whether the retried mutation succeeded.

Acceptance criteria

• A 401 during a mutation triggers the existing inline re-auth banner
• Successful re-auth automatically retries the original mutation exactly once
• A second 401 after retry shows a clear failure message rather than looping
• Verified for at least role assignment and policy update mutations

Likely affected files/directories

• lib/api/live.ts
• lib/wallet/providers.tsx (SiweAuthContext)
• components/admin-guard.tsx

[OlaGreat]

I'd like to take this on. I'm a software engineer with experience in blockchain, backend systems, and open-source contribution. I've reviewed the issue and I'm confident I can deliver a clean implementation with tests covering the acceptance criteria. Happy to follow the project's existing conventions.

[grantfox-oss]

🦊 GrantFox — @OlaGreat has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #327)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@OlaGreat's PR #365 was approved and merged by @Lakes41.

🏆 @OlaGreat: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (872 total points). Track your full progress on GrantFox.

👏 Great work, @OlaGreat! Keep contributing to Adamantine-guild.