[Fizzadar]

Boot and RTM connection failures now share one classifier: revoked or invalid tokens send BAD_CREDENTIALS and log the user out, while deactivated accounts, disabled workspaces and removed users send BAD_CREDENTIALS with a restart action. Network, 5xx and rate-limit failures at boot send TRANSIENT_DISCONNECT and retry inside the connector with capped, jittered backoff, which Disconnect cancels at any point, so they no longer end in UNKNOWN_ERROR. When the RTM websocket fails to connect, the bridge now checks the token with auth.test, so a token revoked during a reconnect is reported instead of retrying forever.

🤖 Generated with Claude Code

[indent]

Issues

All clear! No issues remaining. 🎉

2 issues already resolved

• The new CompareAndSwap only guards the end of connect(). With DMOnly set, connect() calls fetchConversationsForSync, which dereferences s.Client; a concurrent Disconnect sets s.Client to nil, and when connect() runs from the retryConnect goroutine the nil dereference crashes the bridge. (fixed by commit 362c572)
  _{Found by Indent Review Agent}
• The new ConnectionErrorEvent handler calls s.Client.AuthTestContext without a nil check. A concurrent Disconnect sets s.Client to nil, causing a recovered panic, and the auth check also runs after the context is already cancelled. (fixed by commit c226618)
  _{Found by Indent Review Agent}

CI Checks

All required CI checks passed on 362c572.

Review agents

Select any unchecked box below to run or rerun that agent.

Passed (1)

• Indent Review Agent · No remaining issues found

Full results

Indent Review Agent

• Summary: No remaining issues found
• Last ran on commit: 362c5721
• Latest result

  {
    "summary": "No remaining issues found",
    "findings": []
  }