The wizard offers a profile, it doesn't overwrite one

Finishing the avatar step published name = the payment-address name and
the default punk under the user's real nostr identity — renaming (and
re-facing) profiles that already existed. Wizard-suggested fields are
fill-only now: they land only where the profile has nothing.

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

1 files changed, 4 insertions, 1 deletions

diff --git a/src/app.js b/src/app.js
index 1d08ac3..24cc56c 100644
--- a/src/app.js
+++ b/src/app.js
@@ -2311,8 +2311,11 @@ function onboardScreen() {
           const fields = { name: addr ? addr.split('@')[0] : undefined, picture };
           // Publishing the profile is a nicety — a signer that can't sign
           // right now (a sleeping phone bunker) must not trap the wizard.
+          // And it's an OFFER: the address-derived name (and, unless they
+          // actually picked one, the default punk) only fills gaps — it
+          // never renames an identity that already has a profile.
           if (fields.name || fields.picture) {
-            try { await featureHook('publishProfile', fields); }
+            try { await featureHook('publishProfile', fields, { fillOnly: o.avatar ? ['name'] : ['name', 'picture'] }); }
             catch (e) { toast(t('onbProfileSkipped')); console.warn('onboarding: profile publish failed —', e.message); }
           }
           o.step = 'success';