Broker-connect gets a skippable onboarding nudge, in addition to Settings

Decision

Onboarding gains a 6th, unnumbered, always-skippable interstitial — "Connect a broker (optional)" — shown once, after step 5 (plan selection) and before landing on the dashboard. It reuses the same broker cards and copy already built for settings-linked-brokers. This extends 2026-09-01-broker-connect-own-phase, which scoped Phase 9's wireframe work to Settings only; it does not reverse that decision — Settings remains the durable, revisit-anytime management surface, and this interstitial is a one-time discovery nudge on top of it, not a replacement.

Why

Requested directly by the product owner while reviewing the Settings wireframes. The earlier framing (Settings-only, no onboarding step) was the right default absent a specific ask — broker-connect is post-signup, optional, and revisit-anytime, so it doesn't fit the onboarding flow's existing mandatory-step shape. But a first-run nudge increases discoverability for a feature a new user would otherwise only find by browsing Settings. Kept strictly optional and unnumbered (not "Step 3 of 3") so it can never be read as blocking, consistent with onboarding-plan's existing "Skip for now" pattern being the only true skip precedent in onboarding.

Impact

• new-user-to-dashboard — new step 6 added, with escapes documented (skip → dashboard; connect → OAuth redirect/callback → dashboard).
• New wireframe .context/designs/web/onboarding/connect-broker.html (unnumbered in-product, filename numbered only for file-ordering).
• New surface page onboarding-connect-broker.
• No change to onboarding-consent or onboarding-plan — this is a new interstitial after both, not a modification to either.
• ROADMAP.md Phase 9 sub-phase 2 (wireframes) updated to note the onboarding nudge alongside the Settings connect-flow mockups.

Status

Active.

Sources

• No .context/raw/ file — direct product-owner instruction in the same chat session as 2026-09-01-broker-connect-own-phase.