migrate

# Migrate Hermit Repo Audit the current repo for safe migration to another machine. Produce a classification of files to migrate, a manifest, bootstrap requirements, and a verification checklist. Git is the source of truth. Migration should be minimal. This skill is read-only — it does not modify files unless you explicitly ask. ## Scoping - `.claude/settings.json` — **project-scoped** (committed). Tracked in git. Migrates with git clone. - `.claude/settings.local.json` — **machine/user-scoped** (gitignored). Contains task list ID (always) and hook permissions + deny patterns (when plugin was installed at local or user scope). Must be recreated on destination — never migrated by git clone. Check `.claude-code-hermit/state/hatch-options.json` `"target"` field: if `"local"`, this file contains hermit's hook permissions and deny patterns; the operator must re-run `/hatch` or `/hermit-evolve` on the destination to restore them. - `.claude.local/` — **machine/user-scoped** (channel state dirs, local overrides). Needs recreation on destination. Never migrated. ## Rules - Do not write or modify any files unless the operator explicitly requests it - Classify conservatively: when in doubt, put a file in DO_NOT_MIGRATE or REVIEW_MANUALLY - `.claude/settings.json` migrates with git clone — never flag it for manual migration or recreation - `.claude/settings.local.json` does NOT migrate with git clone — flag for recreation on destination - `.claude.local/` must be recreated on dest...