invest-setup

# Invest Setup Skill **Single responsibility**: turn an empty openInvest deployment into a working one. **Triggers only on the user's first-time setup** — run once, then step aside (the `invest` skill takes over all day-to-day interaction). ## When to Use - User explicitly says "set up invest" / "initialize invest" / "帮我初始化 invest" - The `invest` skill's `doctor` returns `status: "needs_setup"` (memory / user_profile missing) - User wants a full reconfiguration (explicitly says "reset" / "重新配置"; requires `--force`) - v1 → v2 schema migration (the user's portfolio.md is in the old format) ## When NOT to Use - User is already onboarded (`doctor` returns `status: "ready"`) → **switch to the `invest` skill** - User wants to view holdings / P&L / run the committee → use the `invest` skill - User wants to track a new asset but is already onboarded → the `invest` skill's `POST /api/holdings` endpoint - User wants to commit / push code → that's a git operation, unrelated to setup If you (the agent) entered this skill by mistake, **exit immediately** and tell the user to use the `invest` skill instead. ## Two onboarding paths | Path | Scenario | Flow | |------|------|------| | **A. Fresh deployment** (default) | User's first time with openInvest; data lives on this machine | "Flow (4 steps)" below | | **B. Connect to an existing hub** | User already runs openInvest on another machine (a server) and wants this machine to share the same data (multi-device) | "Path B" below, 2 mi...