Platform Generation v2 — Phase I-B: Library Consolidation (Bridges)

For agentic workers: REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Set up re-export bridges so old import paths keep working, then migrate consumers incrementally as files are touched for other work.

Architecture: Instead of migrating 81 files at once (risky, high churn), create re-export bridges in the deprecated libraries. Old imports resolve to the new canonical location. Full migration is incremental — update imports as files are modified for feature work.

Consumer counts: ui-core (40 files), ui-feedback (29 files), ui-forms (8 files), layout-builder (4 files)

Tech Stack: TypeScript path aliases, NX library re-exports

Strategy

Phase I-B uses re-export bridges instead of mass migration:

1. Unique components from libs-ui-core stay in place for now
2. Duplicate components (button, card, input, select, checkbox, toggle) — consumers should prefer ui-framework versions, but old imports still work
3. Layout-builder stays until vibe-universe consumers are migrated (4 files)
4. No library deletions in this phase — just marking intent

This approach delivers zero risk and unblocks Phase II immediately.

Status: DEFERRED TO INCREMENTAL

This phase is intentionally lightweight. The 81-file migration happens organically as part of Phase II-IV feature work — every time we touch a file that imports from a deprecated library, we update its imports. No dedicated migration sprint needed.