Onboarding, tutorial & help — chat-first, cloud login (MVP workstream kickoff)

[lalalune]

This is the coordination thread for the onboarding/tutorial/help workstream of
the LifeOps Personal Assistant MVP (GitHub project 15). Research doc (read it
before claiming anything): packages/docs/ongoing-development/research/04-onboarding-tutorial-help.md.

Doctrine and decisions adopted

• Onboarding happens in chat. The in-chat conductor is the onboarding
  surface; there is no separate wizard. Status widgets, thinking indicators,
  boot trouble, and recovery all appear in the chat (PR feat(#13377): boot trouble speaks in chat — no floating banners, no canned suggestions, full→half onboarding detent #14168 finishes this —
  it is one of our issues).
• MVP onboarding = one step: sign in with Eliza Cloud. The runtime chooser
  (local / remote) stays behind VITE_ELIZA_ENABLE_RUNTIME_CHOOSER /
  eliza:enable-runtime-chooser (verified: packages/ui/src/first-run/first-run-runtime-flag.ts).
  Cloud-locked Android builds can never re-enable it. We test the flag boundary;
  we do not build live lanes for the flagged local path.
• The tutorial is chat-native (packages/ui/src/tutorial/) and never
  auto-launches — reachable from the launcher tile, /tutorial, typed
  "start tutorial", and the seeded notification. No new tour steps for MVP.
• Help is agent knowledge, not a view. HelpView is deleted (feat(ui): chat-native tutorial service + Help→default-knowledge migration (#13377) #13394); the
  FAQ ships as help-tagged default knowledge
  (packages/agent/src/runtime/default-help-documents.ts) and the chat answers
  it. Our job is proving that works with a live model, not rebuilding UI.
• Minimal scope. No new onboarding features. This workstream is fixing,
  testing, and verifying what exists. Prefer deleting (e.g. the post-onboarding
  character-select detour, pending owner confirm) over adding.
• The verification of record is the live lane. Mocked keyless Playwright
  lanes are the regression net; app-live-e2e.yml + device lanes with a real
  Eliza Cloud account and a real LLM are what "works" means. That lane is
  currently red — fixing it is the P0.

Issues (most important first)

1. [onboarding] P0 — Resurrect App Live E2E: real cloud login + real-LLM chat must produce a green nightly run
2. [onboarding] P0 — Device e2e for the default cloud sign-in onboarding via the SIWE e2e wallet (iOS sim + Android emu)
3. [onboarding] P1 — Liveness contract: every onboarding e2e ends with a real chat turn and a non-stub reply
4. [onboarding] P1 — Scenario: agent answers help questions from seeded help knowledge (live LLM, trajectory reviewed)
5. [onboarding] P1 — Land in-chat boot recovery (PR feat(#13377): boot trouble speaks in chat — no floating banners, no canned suggestions, full→half onboarding detent #14168): rebase, resolve, verify no floating banners remain
6. [onboarding] P2 — Remove the one-time character-select landing after cloud-only onboarding (owner confirm, then delete)
7. [onboarding] P2 — Onboarding test hygiene: inline MP4/JPG evidence, drop .github/issue-evidence writes, chooser-lock assertions

Suggested order: 1 and 2 can run in parallel (different infra). 3 depends on 1
(the shared helper lands where the live lanes are green). 4 is independent. 5 is
independent but rebases across whatever else merges — claim it early or last,
not mid-stream. 6 needs an owner comment before code. 7 is safe filler.

How to claim work

• Comment on the issue ("claiming — session/branch ") and move the
  card on project 15 to In Progress. One issue per agent at a time.
• Branch as fix|feat|test/<issue#>-<slug> off develop; PR against develop.
• Sync before opening/updating a PR: git fetch origin && git rebase origin/develop,
  bun install, bun run verify. Check the issue is still open and the target
  files haven't been rewritten on develop before you start — this area moves
  fast (feat(ui): chat-native tutorial service + Help→default-knowledge migration (#13377) #13394 merged mid-research).
• If you discover the issue is stale/solved, say so on the issue and close it
  with the evidence — don't re-implement.

Evidence rules (binding — note the NEW mechanics)

PR_EVIDENCE.md still defines what must be proven, but artifacts are now posted
inline in the GitHub issue/PR, not committed to .github/issue-evidence/:

• MP4 for videos (renders inline in GitHub) — full-flow walkthroughs and
  device recordings. Convert simctl / adb output if needed.
• JPG for screenshots (size) — always include the WRONG behavior first for
  bug fixes, then the fixed state; desktop and mobile where applicable.
• Logs, trajectories, and report JSON go in collapsed <details> blocks; redact
  tokens.
• Real means real: live Eliza Cloud account, live LLM turn, real device or
  simulator. A mocked lane can supplement but never substitute. Read every
  trajectory you attach — capturing is not reviewing.
• Each evidence type is attached or explicitly N/A — <reason>. Never blank.

Filed issues

• [onboarding] P0 — Resurrect App Live E2E: real cloud login + real-LLM chat must produce a green nightly run #14357 — P0 [onboarding] P0 — Resurrect App Live E2E: real cloud login + real-LLM chat must produce a green nightly run
• [onboarding] P0 — Device e2e for the default cloud sign-in onboarding via the SIWE e2e wallet (iOS sim + Android emu) #14358 — P0 [onboarding] P0 — Device e2e for the default cloud sign-in onboarding via the SIWE e2e wallet (iOS sim + Android emu)
• [onboarding] P1 — Liveness contract: every onboarding e2e ends with a real chat turn and a non-stub reply #14359 — P1 [onboarding] P1 — Liveness contract: every onboarding e2e ends with a real chat turn and a non-stub reply
• [onboarding] P1 — Scenario: agent answers help questions from seeded help knowledge (live LLM, trajectory reviewed) #14360 — P1 [onboarding] P1 — Scenario: agent answers help questions from seeded help knowledge (live LLM, trajectory reviewed)
• [onboarding] P1 — Land in-chat boot recovery (PR #14168): rebase, resolve, verify no floating banners remain #14361 — P1 [onboarding] P1 — Land in-chat boot recovery (PR feat(#13377): boot trouble speaks in chat — no floating banners, no canned suggestions, full→half onboarding detent #14168): rebase, resolve, verify no floating banners remain
• [onboarding] P2 — Remove the one-time character-select landing after cloud-only onboarding (owner confirm, then delete) #14362 — P2 [onboarding] P2 — Remove the one-time character-select landing after cloud-only onboarding (owner confirm, then delete)
• [onboarding] P2 — Onboarding test hygiene: inline MP4/JPG evidence, drop .github/issue-evidence writes, chooser-lock assertions #14363 — P2 [onboarding] P2 — Onboarding test hygiene: inline MP4/JPG evidence, drop .github/issue-evidence writes, chooser-lock assertions

---

Design doc · MVP board