Bug: DELETE /auth/:providerID does not invalidate Provider state cache

[digi4care]

Description

When removing an auth provider via DELETE /auth/:providerID, the Provider.state() cache is not being invalidated. This causes the provider to still appear as "connected" even after successful removal.

Steps to reproduce

1. Add a provider auth (e.g., POST /auth/opencode)
2. Verify provider shows as connected in GET /provider
3. Remove the auth via DELETE /auth/opencode
4. Check GET /provider - provider still shows as connected (BUG)

Expected behavior

After DELETE /auth/:providerID, the provider should no longer appear as connected in subsequent /provider requests.

Root cause

In packages/opencode/src/server/server.ts, the DELETE handler calls Auth.remove(providerID) but does not invalidate the Provider state cache. The Provider.state() function caches provider data, and this cache is not cleared after removing auth.

Fix

Add await Instance.disposeAll() after await Auth.remove(providerID) to invalidate the state cache.

---

[github-actions]

This issue might be a duplicate of or related to existing issues. Please check:

• Google config provider cannot be disconnected (optimistic update only) #12384: Google config provider cannot be disconnected (nearly identical symptom)
• Cannot disconnect from provider #10494: Cannot disconnect from provider (same issue category)
• fix: multiple memory leaks in long-running sessions #10913: Multiple memory leaks in long-running sessions (mentions missing Instance.disposeAll() calls, which is your proposed fix)

You may want to reference these issues or check if they've already been addressed.

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.