Fix: gate forced 2FA onboarding handoff on real hasCompletedGuidedSetupFlow

Co-authored-by: Rory Abraham <roryabraham@users.noreply.github.com>

Author: MelvinBot

src/pages/settings/Security/TwoFactorAuth/DynamicSuccessPage.tsx

@@ -56,7 +56,9 @@ function DynamicSuccessPage({route}: DynamicSuccessPageProps) {
     const isIncompleteOnboarding = hasCompletedGuidedSetupFlow === false;
     const hasSavedOnboardingPath = !!onboardingInitialPath?.includes(`/${ROUTES.ONBOARDING_ROOT.route}`);
     // Forced onboarding 2FA always enters via Settings > Security (from the require-2FA overlay).
-    const isForcedOnboardingHandoff = AccountUtils.isForced2FAOnboardingSetup(account, false) || (!!account?.requiresTwoFactorAuth && isIncompleteOnboarding && hasSavedOnboardingPath);
+    // Gate on the real hasCompletedGuidedSetupFlow so the handoff only fires for users who haven't finished
+    // guided setup; passing a literal false made it fire for every user setting up 2FA from Settings > Security.
+    const isForcedOnboardingHandoff = AccountUtils.isForced2FAOnboardingSetup(account, !!hasCompletedGuidedSetupFlow) || (!!account?.requiresTwoFactorAuth && isIncompleteOnboarding && hasSavedOnboardingPath);
     const shouldReturnToOnboardingAfter2FA = isSecuritySettingsFlow && isForcedOnboardingHandoff;
 
     const completeForcedOnboarding2FAHandoff = () => {