Onboarding, inside Settings

1. It lives in Settings, as its own group. A new Onboarding group sits at the top of the Settings menu until go-live: Overview, Leasing, Maintenance, Renewals. Every page is under /settings/onboarding/…, inside the normal Settings frame, so clicking a module never leaves Settings. After go-live the group drops to the bottom as a record. The Company group loses its "Onboarding & go-live" row (it became Overview). The other option, sub-pages under Company › Onboarding & go-live, buries the most important thing a new customer does three levels deep.
2. Each module explains before it asks. A one-line "what Clara does here" plus a five-step flow, where each step names the question step that controls it, the same way the blueprint's timeline does. Then the sections become numbered steps with Back and Next, one at a time, with "N of 25 answered" always in view.
3. Big choice cards wherever the answer has a real shape. Tour length, travel time, office hours, the application link, who handles escalations, ring order, renewal rent. Typed answers stay as text, with tap-to-fill examples for the yes-or-no ones. Choices save the moment you tap (the same write the Save button does today); typed answers keep a Save button, so we never store half a sentence.
4. "Recommended" appears only where we really have one. Only tour length (30 minutes) and travel time (none, "our default") get the badge, because those are the only questions on these pages that acceptRecommendationPlan allows. Renewal limits show "used until you answer" instead: Clara does use 2 months owed and 2 late payments today, but the code deliberately refuses to call the customer's money our recommendation. Office hours get a quick preset, not a badge.
5. Same rules underneath, plus warmth on top. Same questions, same writers, same pending dots (smaller, amber, never after go-live), same read-only-after-go-live rule. The brand gradient and logo come from the blueprint. Copy says "Propflow" (lowercase f, the brand rule); the app's existing strings still say "PropFlow" and change in the copy part.

From origin/main on 2026-10-01. "Counts" = it is in ONBOARDING_MENU[].fields, so it can hold a dot and shows in "N left". Labels in the middle column are today's; the mock rewrites them as plain questions.

Totals a customer sees: Leasing 25, Maintenance 3 (2 they can answer), Renewals 2.

1. Maintenance always shows one left that the customer cannot answer. maintenance.intake_route is read-only for customers ("Propflow sets this up with you") but it is not in PROPFLOW_ONLY_FIELDS, so it holds a dot and counts toward "N left" until staff set it. The mock shows it as "Propflow sets this up" and leaves it out of the count. Fix: add it to that list, a few lines in its own PR.
2. Renewal limits: a "Keep what Clara uses now" card would save the engine's numbers as the company's own answer. That is the customer choosing a value, not us recommending one, but it does clear the dot. Gera's call before part 6 ships it; until then part 6 keeps "Set my own limits" only.
3. Knowledge titles are load-bearing. Building answers override company answers by matching the title text. The plain-language rewrite changes only label and help, never title.
4. Hours & contact "Coming soon" rows only show to system admins today. The mock keeps that, so customers don't see six greyed-out rows on their first page.

Routes

• ONBOARDING_GUIDE_HREF becomes /settings/onboarding. Every section href, sectionForPath, the hub rows and the dots all read from it, so it is one constant.
• Section pages move from (workspace)/onboarding-guide/<module>/<section> to (workspace)/settings/onboarding/<module>/<section>, which puts them inside the Settings layout and menu with no new shell.
• Redirects: /onboarding-guide/** → the same path under /settings/onboarding; /onboarding-guide and /settings/go-live → /settings/onboarding. Same pattern as the old Knowledge page's redirect. Bookmarks and old emails keep working.

Components

• settings-menu.ts: new group onboarding (Overview + one item per ONBOARDING_MENU tab; activeSettingsMenuHref already lights a module for every section under it); placed first before go-live, last after. company-topics.ts: go-live leaves COMPANY_TOPIC_PAGES. The menu test and the census test move in the same PR as the routes.
• OnboardingGuideShell → OnboardingModuleFrame: drops its own PageHeader, TabBar and back link (the Settings menu replaces them) and keeps the status, read-only and dots context. Adds the intro, the flow, the stepper with "x of y" and Back/Next.
• onboarding-menu.ts gains copy only: intro and flow per tab, intro per section. Still imports nothing.
• New ChoiceCards (check the component library for a radio-card piece first). TextAnswerQuestion gains choices; the badge reads ctx.recommended, so it cannot appear where acceptRecommendationPlan refuses. KnowledgeQuestions gains optional quickAnswers that fill the same text.
• Hub: PreLaunchChecklistCard + onboarding-hub-rows.tsx keep their data (onboardingModuleRows, the customer rows) and get the progress hero and module cards.

Slices: each part branched off origin/main, each works on its own

Order: part 1 first, since every later part uses its routes. Then parts 2, 3 and 4 open together, up to three at once, each off fresh origin/main. Parts 5 and 6 come after part 4, because they use the cards.