fix(desktop): refresh pending sign-in after every continue and gate on shell support

Re-read the chat's pending sign-in after any continue result so a failed
launch that retired the previous handoff cannot leave a stale notice, and
require the shell's continue-sign-in bridge before showing the feature, since
the profiles cache is shared with the import dialog on older shells.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/home/components/mothership-view/components/resource-content/components/browser-session/use-continue-sign-in.ts

@@ -51,14 +51,17 @@ interface UseContinueSignInProps {
 export function useContinueSignIn({ scopeId, pageUrl }: UseContinueSignInProps) {
   const supported = supportsContinueSignIn()
   const { data: profiles = [] } = useBrowserImportProfiles(supported)
-  const { data: pending = null } = usePendingSignIn(scopeId, supported)
+  const { data: pendingData = null } = usePendingSignIn(scopeId, supported)
+  const pending = supported ? pendingData : null
   const { mutateAsync: startHandoff, isPending: starting } = useStartSignInHandoff(scopeId)
   const { mutateAsync: importBack, isPending: importing } = useBringSignInBack(scopeId)
   const { mutate: cancelHandoff } = useCancelSignInHandoff(scopeId)
   useSyncExternalStore(subscribeToDismissals, dismissalCount, dismissalCount)
 
   const page = parseHttpsPage(pageUrl)
-  const canContinue = profiles.length > 0 && page !== null
+  // The profiles cache is shared with the import dialog, which older shells
+  // also support, so cached profiles alone must not reveal this feature.
+  const canContinue = supported && profiles.length > 0 && page !== null
   const hintHost = page ? signInHintHost(page) : null
   const hintVisible =
     canContinue && pending === null && hintHost !== null && !dismissedHintHosts.has(hintHost)

apps/sim/hooks/queries/browser-import.ts

@@ -67,6 +67,10 @@ export function useStartSignInHandoff(scopeId: string) {
     onSuccess: ({ pending }) => {
       if (pending) queryClient.setQueryData(browserImportKeys.pendingSignIn(scopeId), pending)
     },
+    // A failed or superseded launch can still retire the chat's previous
+    // handoff, so the shell's answer replaces whatever the cache last held.
+    onSettled: () =>
+      queryClient.invalidateQueries({ queryKey: browserImportKeys.pendingSignIn(scopeId) }),
   })
 }