sutando-migrate

Sutando Migrate

Guided workspace migration for existing users (M1 Part 2). Reach for this when:

• The legacy-state-detected warning fires (health-check, init.sh, check-pending-questions)
• A user has data at a pre-M0 location (<repo>/{notes,state,results,...}/, ~/.sutando/workspace/, or a custom $SUTANDO_WORKSPACE-pointed path) and wants it folded into the M0 canonical <repo>/workspace/
• Owner explicitly says "migrate workspace" or "run sutando-migrate"

Usage: /sutando-migrate [--auto]

--auto proceeds without per-step greenlight. Without it the skill waits for owner OK at each phase boundary.

What this skill does (5 phases)

Phase 1 — Scan + summary

Run bash scripts/sutando-migrate.sh scan --json. Parse the JSON for:

• Total unique relpaths across A+B+C+dest
• Per-source byte counts
• Cross-source collision triage: identical_content (drop-dup, no action) + mtime_only_diff (commit's newest-mtime auto-resolves) + size_mismatch (REAL content conflicts — owner attention)
• Notable size-mismatch entries (build_log, conversation.log, state/* divergences)

Present a concise 4–6 line summary to owner via:

• Discord DM (text)
• macOS notification (osascript -e 'display notification "scan ready: N actionable / M ignorable" with title "Sutando-Migrate"')
• If voice client connected, a brief voice summary

Wait for greenlight unless --auto.

Phase 2 — Commit (data move)

If owner says go:

• bash scripts/sutando-migrate.sh commit (no --delete-source; honors workspace_m1_no_auto_commit)
• Surface the commit-output to owner: backup-id, per-source counts (copied/identical-drop/kept-dest/sidecar/skipped), sentinel paths

After commit, the script prints the phase-2 footer ("After ~7d run --commit --delete-source --backup-id "). Acknowledge it; don't run delete-source automatically.

Phase 3 — Verify

• bash scripts/sutando-migrate.sh verify — confirms hash + count match per indexed source-file entry
• If verify FAILS (returns non-zero), report the failure + suggest rollback. Don't proceed.