[Feature] Proposal: read-only extraETF portfolio import for allocation and rebalancing insights

Problem or Motivation

extraETF is widely used by German-speaking ETF investors to consolidate portfolio holdings. Today, Vibe-Trading has connector-first account and position reads, but no way to bring an extraETF portfolio into those existing portfolio-analysis workflows. Users must manually re-enter holdings before they can assess allocation drift or receive rebalancing insights.

Proposed Solution

Add an opt-in, read-only extraETF portfolio import that normalizes account and position data into Vibe-Trading's existing connector model. The initial feature would:

• expose imported portfolio snapshots through the existing account/position read surfaces;
• show source and snapshot freshness;
• generate transparent rebalancing proposals from a user-defined target allocation;
• remain strictly non-executing: no orders are sent to extraETF or any broker;
• avoid capturing passwords, cookies, or sessions.

The preferred implementation order would be:

1. a documented official API, if extraETF offers and permits one;
2. an official user-exported CSV import as the likely V1;
3. only if acceptable under extraETF's terms and technically stable, a separate user-triggered browser-extension sync as an opt-in V2.

Current research suggests that an official public third-party portfolio API may not be available, so an exported CSV appears to be the safer baseline. This needs confirmation before implementation.

Questions for maintainers

1. Does this fit the project's connector-first product direction?
2. Should V1 be limited to an explicit local CSV import, with browser integration kept out of scope?
3. Are there existing privacy, storage, or connector conventions beyond the current read-only profiles that a contribution must follow?
4. Would a contributor PR be welcome after the supported extraETF access path and data schema are confirmed?

Alternatives Considered

• Browser extension: could improve freshness but would rely on a private web UI and requires careful review of extraETF terms, permissions, and privacy. It should not block a safe import-based V1.
• Direct scraping/login automation: not proposed for V1 because it is brittle and risks handling sensitive session material.
• Manual entry only: works today but loses portfolio import and refresh benefits.

Scope boundary

This proposal is for portfolio reads and analysis only. Automated trading, order submission through extraETF, and automatic broker execution are explicitly out of scope.

Contribution

I am willing to prepare a PR once the maintainers agree on the integration path and scope.