nativephp-v3-to-v4-upgrade

Follow the phased plan: move composer packages from nativephp/native-ui to nativephp/mobile-ui with a vcs repository and inline branch alias, register the plugin with native:plugin:register, then scaffold layouts and routes before converting screens one by one. Strip Livewire providers before running composer remove to avoid fatal errors during package discovery.

Fonts not working usually means the theme push fired before the bridge was reachable, so the native side keeps its system font and empty alias map. Re-push the theme after the container boots with $this->app->booted(fn () => Theme::pushToNative()), and ensure each font attribute has a matching weight class like font-extrabold.

An empty native:column paints nothing because the renderer returns Color.clear when a node has no children, discarding background and size. Use a self-closing native:rect for solid fills or scrims, and remember absolute children are anchored at their measured size rather than stretched by opposing insets.

The native:font command ships in the nativephp/mobile-ui package, not nativephp/mobile. It downloads Google Fonts into resources/fonts, and the plugin's copy_assets build hook bundles them into native projects during native:run.

Unsupported classes are silently dropped by TailwindParser, including blur-*, scale-*, per-corner radii like rounded-t-xl, and max-w-*/min-w-*. Verify any class with TailwindParser::parse() returning an empty array before assuming it works; gradients and inset-* are supported.

Port legacy Livewire tests to Native\Mobile\Testing\Native::test() or Native::visit() with FakeBridge and Saloon MockClient, covering happy, failure, and offline paths. Note the test harness renders through createElement, a different code path from the device's streaming collector, so verify props on both.