codex-claude-migrationlisted

# Codex and Claude Migration Use the bundled engine for deterministic discovery, copying, hashing, linking, rollback, and audit. Use model judgment only to resolve ambiguous project ownership or version-specific state formats. Require Python 3.12 or newer. Windows migration uses native junction detection; macOS and Linux use symbolic links. The engine blocks older runtimes before inspecting or changing data so link boundaries cannot be misclassified. ## Start 1. Read [interaction-contract.md](references/interaction-contract.md). 2. When the user invokes this Skill to migrate, treat `move` as the intent. Do not ask whether to audit, back up, or migrate: audit and a verified staged copy are mandatory internal migration phases, and retained source backups are created before links change. Use `backup`, `restore`, `attach-portable`, or audit-only only when the user explicitly asks for that different operation. 3. Guide the user through the migration choices in this order: - products: Codex, Claude, or both; - absolute destination/package parent; - project scope: discover all, then show every candidate project and session with its name and one- or two-sentence summary; projectless sessions remain projectless; - credential policy: `standard` (default: normal login state, no recognized API credential files), `complete` (all recognizable login/API state), or `none` (no login state). Standard scans supported structured/text config keys; a mixed file containing a recogni