Onboarding: 'Skip setup entirely' leaves Me persona uncreated (intentional or gap?)

[shiba4life]

Observation

On the Personas sub-tab of People, the empty-state copy reads:

No personas yet. The Me persona is created at node signup; other personas appear as you group fingerprints together.

If "node signup" means "completing the onboarding wizard," then choosing Skip setup entirely on step 1 never creates the Me persona. A user who skips ends up in a permanent "no personas" state until they manually trigger something, with no guidance on what.

Two possible intents

1. Intentional: skipping = "I'm an advanced user, leave me alone, I'll create personas explicitly later." Fine, but the Personas empty-state copy is then misleading — it promises Me at signup and quietly didn't deliver.
2. Gap: skipping should still bootstrap the minimum persona state. Me is the anchor all other personas cluster against; being in zero-persona-state is probably not a supported app configuration.

Either way, the Personas empty-state copy and the Skip button's behavior don't agree. One should change.

Repro

1. Fresh node, open http://localhost:5175.
2. Onboarding wizard step 1 (Identity) shows.
3. Click Skip setup entirely at the bottom.
4. Navigate to People → Personas. Empty state claims Me is created at signup, but no persona exists.

Suggested direction (pick one)

• Option A (gap fix): create the Me persona as part of the "skip" path too, using sensible defaults (e.g. display name derived from user_hash). The wizard becomes pure UX polish, not a required state-creation step.
• Option B (copy fix): change the Personas empty-state to "No personas yet. Complete the onboarding wizard (Settings → Profile) or create one from a fingerprint cluster below."

Severity

Low (user can still use the app; the mismatch is a papercut).

Context

• Found by /qa-only on 2026-04-18.
• QA report: .gstack/qa-reports/qa-report-localhost-5175-2026-04-18.md.
• gbrain slug: agent/findings/qa-fold-db-node-dashboard-2026-04-18.