Track language binding support on Android

[sargunv-bot]

CI builds the C API and the Rust, Go, Kotlin/Android, Dart, and Zig bindings for every Android preset. The C API and the Rust, Go, Kotlin/Android, and Zig suites run on an x86_64 Android emulator for both android-x64-egl and android-x64-vulkan. The Python suite runs on android-x64-egl. Arm64 remains build-only, and Dart remains build-only on every Android target.

Status values:

• Tested — CI runs this binding's own suite on the emulator.
• Built — CI builds this binding for Android, and nothing executes.
• Not started — no Android coverage yet.
• Blocked — an upstream toolchain gap has to close first.
• Not applicable — another binding covers Android.

Binding	Status	Work required
Rust	Tested	None. The x64 EGL and Vulkan suites run; arm64 stays build-only.
Go	Tested	None. The x64 EGL and Vulkan suites run; arm64 stays build-only.
Kotlin/Android	Tested	None. The x64 EGL and Vulkan suites run; arm64 stays build-only.
Zig	Tested	None. The x64 EGL and Vulkan suites run; arm64 stays build-only.
Python	Tested	Add x64 Vulkan coverage. The device harness currently accepts only x64 EGL, installs PyOpenGL but not the Python Vulkan fixture dependency, and needs an Android libvulkan.so loader path.
Dart	Built	Add a small Flutter Android host that invokes the native-assets hook, packages the Rustls verifier helper, and calls mln_android_init. Run it on the x64 emulator once that host is stable.
C#	Not started	Large: add a net10.0-android target, package native assets, adapt native loading, initialize JNI state, and add an application and emulator test host.
Swift	Blocked	The official Swift Android SDK cross-builds the binding but does not provide the Testing module. Add device tests when upstream supports them, or add an application smoke host.
Kotlin/Native	Not started	Add Android Kotlin/Native build and emulator test coverage.

A binding reaches Tested by running its own suite on the emulator. That suite calls the ABI version, creates a runtime, and exercises a headless render or an application smoke test. The x64 emulator provides SwiftShader GLES and Vulkan. Arm64 targets stay build-only until CI gains an arm64 device runner.

[sargunv-bot]

Initial CI slice: #526 adds build-only Go and Rust coverage for Android arm64 and x64 against both OpenGL and Vulkan. Runtime emulator coverage and the remaining bindings stay tracked here.

[sargunv-bot]

Emulator slice: #532 boots an x86_64 AVD through mise and runs the C API, Rust, and Go suites on android-x64-egl. Arm64 and Vulkan stay build-only, and the remaining bindings stay tracked here.

[sargunv-bot]

Kotlin/Android is now Tested: #586 adds and runs its 18-test device suite on the android-x64-egl emulator in CI. Arm64 and Vulkan remain build-only.

[sargunv-bot]

Remaining-binding pass:

• Zig: Run the Zig binding tests on Android #598 cross-builds every Android target and runs all five test executables on the x64 EGL emulator; its CI is green.
• Python: Run the Python binding tests on Android #599 cross-builds a CPython 3.14 Android wheel and runs the binding suite in CPython’s device testbed; 138 tests pass, and the full Android x64 EGL CI job is green.
• C#: passed for now because it still needs a net10.0-android target, Android workload, APK/device-runner host, native asset packaging, and JNI initialization.
• Swift: passed for now because the official 6.3.1 Android SDK cross-builds the binding but does not provide the Testing module; upstream still qualifies Swift Testing on Android as experimental and build-only.