invest-backup

# Invest Backup Skill ## Why this skill exists openInvest's real data (holdings/strategy/user profile/committee records under `memory/`, trade ledger/job history under `db/`) is **entirely `.gitignore`d** — deliberately (privacy: it contains real assets/salary/trades), but the price is that git can't help at all. There was an incident on 2026-07-08: a one-off migration script named `migrate_profile.py` (with no safety guard whatsoever) was run directly once, overwriting `user.md` / `strategy.md` / `portfolio.md` with hard-coded demo defaults; `daily_report` then exited early every day because `target_assets` had become empty, emails stopped entirely from that point on, and the user had no idea until they noticed the missing emails and traced it back. **In any of the following scenarios, proactively use this skill**: - Before running any unfamiliar migration / init / bulk script that writes to `memory/` or `db/` → `backup` first - The user says holdings, strategy, or committee records look wrong / wiped → `backup` first (even if the current state is already broken, save the "broken state" — otherwise you lose even the diagnostic material), then investigate - Migrating to a new machine / reinstalling the deployment → `backup` to package, `restore` on the new machine ## Usage ```bash plugin/skills/invest-backup/scripts/run.sh backup [output_dir] # defaults to $INVEST_ROOT/.backups/ plugin/skills/invest-backup/scripts/run.sh restore <zip_path> [--force] plugin/skills/inves...