Migrate Radix To Base

It knows how to handle shadcn projects by fetching golden pairs from the registry and replaying your customizations onto the Base UI variants using three-way merges, while hand-rolled Radix code gets transformed using prop tables and pattern matching. The strangler-fig approach is smart: writes migrated components to separate files, moves consumers over one at a time, keeps everything buildable. It's opinionated about git hygiene (clean tree, feature branch, one commit per component) and won't silently patch behavior differences. If you're stuck on Radix because migration sounds painful, this actually automates the tedious parts.