Simplify setup journeys with guided phone pairing and bot creation

[sambitcreate]

Setup currently makes people coordinate separate settings before they can connect a phone or start useful work. This change adds guided setup and clearer recovery across the approved UX review, with ChatGPT, LM Studio, Ollama, and Other Custom Provider shown before Other ways, and consistent Create a bot wording.

• Phone pairing uses two setup cards and one acknowledgement. A serialized main-process operation checks prerequisites, enables the chosen connection, verifies pairing, and rolls back newly introduced access on known failures. Existing routes, device identity, one-use codes, and uncertain-outcome reconciliation are preserved.
• Bot creation becomes two steps with optional appearance/capability details and minimal Custom access for fresh desktop drafts. Existing bots retain their policies.
• Telegram, voice, Computer Use, schedules, plugins, and Settings search gain clearer setup groups, access explanations, connection checks, and draft/error recovery. iOS/Android pairing directions follow the new desktop flow.

Review the Now vs proposed HTML, implementation checklist, and 39-journey audit/backlog. Two desktop actions assumes the connection method is already selected and external prerequisites are ready; phone scanning and OS/account permissions are additional steps.

Validation

• All 8 selected Electron walkthroughs pass, including real local-fixture onboarding/relaunch, guided LAN cancellation/pairing, permission cancellation, and Settings navigation. The Bot editor test uses a test-owned IPC catalog to verify submitted access and failed-draft retention; native Keychain persistence is covered separately and is not claimed by that UI test.
• Remote: 374 passed, 1 existing skipped; onboarding: 51; bots: 431; voice: 73; Telegram: 181; scheduling: 98; focused UI/plugin/permission contracts: 33.
• Android debug unit suite/build, desktop/E2E TypeScript, changed-file ESLint, Vite and Electron bundles pass. React Doctor has warnings for large components/state patterns, no errors.

Remaining release gates

Draft pending physical iOS and live Tailscale/phone acceptance. The active Xcode license blocks iOS tools and the normal native-build wrapper; unchanged desktop C helpers were compiled with the installed Command Line Tools and existing flags. The isolated Electron profile cannot establish native Bot Keychain authority; production does not add a fallback. The broader audit remains Active rather than claiming every journey branch is complete.