migration-api

To migrate component APIs from 1st-gen to 2nd-gen while preserving type safety, move properties, methods, and types into core, isolating generation-specific logic to maintain consistent public contracts.

The Phase 3 API migration workflow identifies public surface changes, preserves core types, and documents temporary changes with @todo notes to ensure a clear and well-structured public API across components.

You should document temporary API changes during a component migration by adding @todo notes directly in the code, ensuring temporary deviations from the public contract are tracked for future alignment.

Yes, 2nd-gen component migration enforces that public API contracts must live in core to maintain type safety, isolate generation-specific logic, and align the project structure with SWC guidelines.

Yes, you can apply the Phase 3 API migration workflow across multiple components simultaneously to ensure they share a consistent public contract and updated documentation during the generation transition.

Centralizing public API contracts in core during generation migration maintains type safety by isolating generation-specific logic, preventing contract drift, and aligning project structure with SWC guidelines.