PRD-114 — Onboarding redesign — INVITED PARTNER variant. The first-run Overview of someone who signed up through a partner invite. They join an existing household, so the questions are age, living situation and KiwiSaver only — no home value, no mortgage, no invite step (SCOPE FR13/FR14). Their answers are stored against them, never the inviter (FR15). One new region, Your SortMe, sits at the top: profile tiles that fill in as the user answers, and the active question beneath them. Six skippable questions with a one-line reason each — age, living situation, home value (owners), mortgage lender + fixed-rate expiry (owners with a mortgage), KiwiSaver provider + balance, partner invite. Progress starts at 43% because name, email and the signup goal already count.

• Rules: chip questions advance on one tap; typed steps keep Next; every step has Back, why-we-ask and Skip; skipped is stored distinctly from "no"; clicks outside the section shake it; the AI trigger is hidden until done.
• Data: answers go to the profile at signup. No bank_accounts rows are created until first real bank connection (the "materialised" state shows the declared Property and KiwiSaver in Connected Accounts after that).
• Variants: invitee.html — an invited partner gets age, living situation and KiwiSaver only (no home value, mortgage or invite).
• Faked here: the save-failed state (simulated once on KiwiSaver), the three invite errors (triggered by specific emails), the lender/provider lists (real endpoints on build), the date picker (real Calendar component on build — must add month/year jump).
• Open: top bar shown neutral (no trial cluster) until the trial starts — confirm; whether prod seeds demo data behind this page (GENERATE_DEMO_DATA_ON_REGISTRATION).