Broker-connect flow is its own roadmap phase, not bundled into V3

Decision

The end-to-end broker-connect flow (link Dhan/Zerodha/Upstox/Angel One, sync holdings, feed Portfolio) — the build-out of 2026-09-01-broker-api-sync-as-source — is recorded as ROADMAP.md Phase 9 — Broker Connect (Portfolio), a standalone phase, rather than folded into the existing V3 "Expense + Portfolio polish" scope.

Why

V3 is 6 specific, already-scoped, schema-bound polish items (portfolio-view-only family route, CG-booked timeline chart, family AI advisor, etc. — see the Versioning section of ROADMAP.md). Broker-connect isn't polish on existing Portfolio surfaces — it introduces a new external-integration surface (OAuth-style linking), a new secrets-storage subsystem the codebase has no precedent for (per-user KMS-encrypted access tokens — every existing secret is a single shared app-wide .env value), a new Firestore collection, and a new wireframe that doesn't exist yet. Bundling it into V3 would understate its size and blur its own exit criterion against the 6 unrelated polish items.

Impact

• ROADMAP.md — new "Phase 9 — Broker Connect (Portfolio)" section added, following the same sub-phase breakdown style as Phase 8 (User-Identity-Entry rewrite): wiki, wireframes, schema, storage, backend, website.
• Does not change V1 launch gating — Portfolio isn't promoted for V1 regardless.
• portfolio-pillar — no change beyond the 2026-09-01-broker-api-sync-as-source amendment already made; this decision only affects roadmap sequencing, not the pillar's own spec.

Status

Active.

Sources

• No .context/raw/ file — originates from the same chat session as 2026-09-01-broker-api-sync-as-source, continuing into /plan-change scoping for the connector flow.