Introduce opt-in first-agent setup - #2804

Why

People with no agents need a clear place to start without being sent into setup at launch. The pinned Bestie destination should introduce agents first, then explain Bestie after creation.

What

• Show a rotating Create an agent shortcut and a Create your first agent landing page. Keep setup opt-in.
• After first-agent creation, show a local welcome with that agent’s avatar and the normal incoming-message bubble. Explain the sidebar shortcut and Buzz help.
• Keep agents from another account or community out of the shared inventory choices. Filter saved rows before deduplication in both host readers.
• Center rotating and assigned Bestie avatars in the sidebar row.
• Enable Bestie by default only on fresh local installs. Preserve existing explicit On/Off and legacy implicit Off in both browser and native storage.

How

Reuse the shared agent creation form, saved Bestie choice and canonical DM. A device-local receipt binds the welcome to the first verified DM for that account, community and agent. A measured timeline intro holds the welcome outside real message rows. It publishes no message, starts no model turn and adds no unread state or message actions. Existing-agent choices and replacements do not create a welcome.

Reuse the plugin settings stores and existing local-install detection. Save resolved Bestie choices through those owners; native default snapshots remain best effort. A deliberate settings reset uses the current On default. A new device, profile, or cleared browser storage counts as fresh, even for an older account.

Risk

The inventory correction affects all consumers of the shared saved-agent library on native and development-broker hosts. It changes no stored identities, membership or credentials and adds no relay reads. The welcome adds a presentation slot to the shared timeline; ordinary history, drafts, sending and threads keep their existing owners.

Main integration: merge commit f06f8d8e brings in main at 345d938c9 without rewriting feature commits. It preserves the local welcome alongside main’s shared Bestie DM launchers, Huddle, actions menu, settings and member controls. Both file conflicts are resolved, and GitHub reports the pushed head as mergeable. Human acceptance of this integrated/defaults build remains pending.

Testing

• Before the latest main integration and default change, the human exercised the real native feature build: first-agent setup, community-scoped choices, sidebar appearance and the local welcome. They accepted the result and requested the final wording refinement.
• Agent re-showed the local welcome in the same native build and verified its visible heading and closing text. No message or agent turn was triggered. Temporary replay code was removed.
• Independent feature, host-scoping, presentation, combined-main and fresh-defaults and follow-up fixture reviews completed with no remaining blockers (9/10 or better).
• One browser case was added and none removed. It controls an avatar rotation between native pointer-down and pointer-up to prove dock activation survives artwork replacement. That native targeting contract cannot be proved in jsdom. The new case failed in both engines before the six-line CSS fix; the full sidenav file then passed 20/20 in Chromium and WebKit with two workers and no retries. The existing colocated test still owns rotation, visibility and reduced-motion policy. The existing cold-start journey now proves fresh Bestie activation and opt-in setup; the upgrade journey proves implicit Off is preserved. The saved-settings journey covers enabling and disabling across reload. State permutations remain in the storage owners, with fail-before evidence for fresh On and legacy Off. Existing Chromium/WebKit journeys exercised the integrated dock, opt-in setup, retained drafts, thread/profile history and close behavior. Existing fixtures/selectors were updated for the creation invitation and Personal space fallback. No screenshot sweeps were run.
• Historical browser baseline before this integration: the unchanged Alt+ArrowUp from a message link preserves native scroll ownership case fails in Chromium and WebKit. The same failure reproduces on the exact incoming main d3d69aaa2 in an isolated worktree. Main now binds that chord to Previous conversation; this PR does not change either contract. Across the initial five-file run and a full rerun of the two corrected files, 82 of 84 distinct cases pass. This was not one fully green 84-case run. No test retries or exclusions were added.
• Focused local checks for the current defaults snapshot passed: bin/pnpm exec vitest run src/plugins/storage.test.ts src/plugins/storage.desktop.test.ts src/plugins/storage-imports.test.ts src/plugins/manager.test.ts (50 tests); bin/cargo test -p buzzodz-plugins (133 tests); bin/pnpm typecheck; and bin/pnpm test:browser tests/browser/plugin-defaults.spec.mjs --project chromium --project webkit --no-deps (10 cases). This is focused macOS evidence, not Linux CI parity.
• Normal pre-push hooks passed on b16c75099: TypeScript, all selected unit tests, design checks and whole-workspace Clippy. DCO passed; hosted CI for this head remains pending.
• Follow-up b16c75099 keeps rotating decorative artwork out of pointer hit testing, so its stable dock tab receives the press. Independent review found no blockers. Focused command: bin/pnpm exec playwright test --config tests/browser/playwright.ci.config.mjs tests/browser/sidenav-polish.spec.mjs --project chromium --project webkit --no-deps --workers=2 (20/20, macOS; not Linux CI parity). No navigation assertions, retries or timeout limits were weakened.
• CI run 42690878853 on f06f8d8e tested synthetic merge 6988d0f against incoming main ac8d5fe1. The Bestie lost-click failure is addressed above. Both Chromium composer-growth React Add complete reaction toggles to the message menu #185 errors also reproduce on a clean exact-base ac8d5fe1 and on 6988d0f, using the unchanged two cases in both engines: Chromium fails both; WebKit passes both. This is focused macOS baseline evidence, not Linux parity or a fix. The separate composer defect remains outside this PR; current-head hosted CI is pending.
• The latest conflict resolution passed an independent review with no blockers and 258 focused tests across 17 files: bin/pnpm exec vitest run src/bundled/bestie src/features/messages/ChannelTimeline.viewport.test.tsx src/app/shell/BestieNavigation.test.tsx src/app/entity-navigation.test.tsx src/plugins/storage.test.ts src/bundled/readmes.test.ts --maxWorkers=2. This covers both parents’ welcome/history and DM-control behavior; it is not browser/native acceptance.
• Follow-up 60abd17c0 makes Bestie explicitly On in active-navigation fixtures and updates the declared-default expectation. All 51 tests passed with bin/pnpm exec vitest run src/app/entity-navigation.test.tsx src/app/pages.integration.test.mjs src/bundled/readmes.test.ts src/plugins/storage.test.ts. A stale Vitest file-module cache caused the separate README failure; documented --clearCache restored the unchanged contract. No assertions or hook checks were bypassed.
• Before the default change, the integrated snapshot passed the native scoped identity-library and isolated IPC tests, plus 678 tests in 16 focused frontend/broker files. A controlled older-history gate now proves the welcome stays hidden until verified history reaches its start; a deliberate mutation demonstrated the timeline regression test fails when the intro is removed.
• Deferred: human acceptance of the integrated build, welcome-specific geometry in both themes at narrow/enlarged-text sizes, protected custom-avatar rendering, and packaged/cross-platform acceptance. The existing Bestie workspace journey exercised both themes, narrow widths and enlarged text, without first-agent welcome provenance. Required CI on the pushed head, DCO and code-owner approval remain merge gates. No current native launch or live-data test was performed.

Generated with Goose