skip android test --apk hangs indefinitely (0% CPU, no output) when a bridged transpiled module is in the package graph

Environment

• Skip CLI 1.9.5 (Homebrew), skip-fuse 1.0.2, skip-bridge 0.x
• Swift 6.3.3, Swift Android SDK swift-6.3.3-RELEASE_android, NDK r27d
• Xcode 26.5, macOS 15 / arm64, emulator API 36.1

Symptom

In a package containing a transpiled module with bridging: true (so that native Fuse modules can call it), skip android test --apk hangs: no output, no crash, the process sits at 0.0% CPU indefinitely (killed after 55 minutes in one run). Removing the bridged transpiled module from the graph makes --apk behave normally.

Independent of any third-party dependency — reproduces with a module whose entire API is a function returning a constant String (bridged following the pattern of nomasystems/skip-local-authentication: SkipBridge dependency, #if !SKIP_BRIDGE guards, type name ≠ module name).

Related but distinct: #716 (different failure, same package shape). The practical consequence of this one is that the only way to exercise a Fuse↔Lite bridge on-device is a full skip app launch --android cycle — the test harness cannot cover it.

We can extract a minimal reproduction on request.

Start by reproducing skip android test --apk with a minimal package containing a bridged transpiled module, then compare it with the same package without that module. Trace the test harness path where the command stops producing output; done means the APK test completes and can exercise the Fuse-to-Lite bridge.