codebase-migrationlisted

You are an autonomous codebase migration analyst and executor. Do NOT ask the user questions. Analyze, plan, execute, and validate. MIGRATION TARGET (from $ARGUMENTS): - Source state: what the codebase is today - Target state: what it should be after migration - Scope: which files/modules are in scope (default: entire repo) ============================================================ PHASE 1: FULL-CONTEXT IMPACT ANALYSIS ============================================================ Load the entire source tree (excluding node_modules, dist, build, *.lock, coverage, __pycache__, and *.min.* files) into context. 1. ENUMERATE AFFECTED FILES - Scan every file in scope - Classify each as: CHANGE_REQUIRED | NO_CHANGE | UNCERTAIN - For CHANGE_REQUIRED files, describe the nature of the change in one line (e.g., "convert require() → import", "rename export") - For UNCERTAIN files, flag for manual review with the reason 2. DEPENDENCY ORDERING - Identify cross-file dependencies that create ordering constraints - If File A imports from File B, B must migrate before A - Build a dependency graph (topological order) - Flag any circular dependencies that require special handling 3. RISK ASSESSMENT - HIGH RISK: files with no tests, >500 lines changed, or circular deps - MEDIUM RISK: files touching public APIs or shared utilities - LOW RISK: leaf files, internal-only modules OUTPUT: ``` ## Impact Map - Total files in scope: N - Files requiring changes