Startup Wizard copy is too technical — rewrite as a plain, welcoming first-run guide (not a status report)

[taylorarndt]

Product area

Onboarding / Startup Wizard / UI copy

Severity

P3 - polish (confusing first-run experience)

Summary

The Startup Wizard (Help → Startup Wizard, and shown on first run) reads like internal release notes, not a welcoming first-run screen. It's built in quill/ui/main_frame.py → _build_startup_wizard_html() (~18185).

Current content:

• A "Current Setup Progress" status table (Setup area / Status / What this controls) — framed as a status report, not guidance.
• A "Guided Flow" numbered list.
• "Accessibility Notes" and an "After Wizard" line.

What's wrong (too technical)

• Internal/jargon language a new user won't understand:
  • "BITS Whisperer rollout setup" / "Set provider/model defaults, readiness checks, and status-page behavior" / "BITS Whisperer onboarding changes setup defaults only; runtime routing remains staged."
  • "feature state", "supported document intake", "Configure engines, paths, voices, and downloads."
  • "Acknowledge responsible AI use, data handling, and user accountability." (legalese)
  • "Open Help > Status Page (HTML Preview) to monitor task activity, feature state, and speech setup health." (overlaps Onboarding/menu copy is too technical: drop "(HTML Preview)" and reword the post-wizard Status Page guidance #75)
• Framing: leads with a "Current Setup Progress" table instead of a friendly "Welcome — here's how to get started."

What to fix

• Rewrite _build_startup_wizard_html() in plain, welcoming language: what Quill is, what each setup step gives the user (in their words), and a warm "you're all set" close.
• Remove or soften internal terms (esp. the "BITS Whisperer rollout / readiness checks / runtime routing" wording) for end users.
• Coordinate with Onboarding/menu copy is too technical: drop "(HTML Preview)" and reword the post-wizard Status Page guidance #75 (drop "(HTML Preview)", reword the post-wizard Status Page line).

Acceptance

• Wizard reads as a friendly first-run welcome, not a status/release report.
• No internal jargon ("rollout", "readiness checks", "runtime routing", "feature state", "HTML Preview", "document intake") in user-facing text.
• Screen-reader users hear plain, task-oriented guidance.

Related: #75.