v0.4.0-beta.1

Fixed

• Hotspot started by the app via the Shizuku binder path now hands out DHCP leases on stricter OEM tethering stacks. The hidden-ITetheringConnector request was missing connectivityScope = CONNECTIVITY_SCOPE_GLOBAL, leaving it at the invalid default 0. Lenient stacks (e.g. Pixel) tolerated this, but stricter OEM stacks brought up only the Wi-Fi AP radio (SSID visible, clients could associate) without starting the downstream DHCP server, so connected devices never received an IP address. Toggling the hotspot off/on from system settings worked because that path builds the request with the correct scope.