A restored login ends the wizard instead of stalling in it

Signing in mid-wizard with a key whose wallet was restored left you on
the sign-in step: the back-button hold matched the restored account and
blocked the auto-advance. A login now clears the hold explicitly — and a
restored wallet skips the rest of onboarding entirely; it was already
onboarded wherever it came from.

Co-Authored-By: Claude Fable 5 <[email protected]>

1 files changed, 8 insertions, 0 deletions

diff --git a/src/app.js b/src/app.js
index 4d0f9e0..2124927 100644
--- a/src/app.js
+++ b/src/app.js
@@ -3597,6 +3597,14 @@ const ctx = {
   getAccount: () => accountSel(),
   // Open (or create) a wallet from a mnemonic — used by nostr login.
   openMnemonic: async (mnemonic, passphrase, opts) => enterWallet(mnemonic, passphrase, opts),
+  // A nostr login that lands mid-wizard: a restored wallet has been through
+  // onboarding elsewhere, so the wizard ends; a fresh one just releases the
+  // back-button hold so the wizard advances to naming it.
+  onbNostrLogin: (restored) => {
+    if (!ui.onb) return;
+    if (restored) { ui.onb = null; try { localStorage.removeItem(ONB_STEP_KEY); } catch {} }
+    else ui.onb.heldFor = null;
+  },
 };
 const FEATURES = buildFeatures(ctx);