Dependency Migration

Map behavior and ownership before changing imports. A successful migration preserves required runtime behavior, lifecycle, data compatibility, and operational expectations—not merely type-checking.

Workflow

1. Identify repository constraints, package ownership, runtime targets, and relevant tests.
2. Classify usages by behavior and lifecycle instead of applying blind replacement.
3. Compare current official guidance, compatibility layers, and related package requirements.
4. Define success evidence and material risks before editing.
5. Migrate in reviewable slices, removing obsolete code introduced by the old dependency.
6. Verify focused behavior first, then broader integration and repository checks.