Android: CoreCLR net11.0-android prototype with Vulkan, Skia, packaged content and lifecycle #235

Current State

No Turian code has run on Android. .NET 11 makes CoreCLR the only Android runtime (UseMonoRuntime=true fails with NETSDK1242), and the assessment only researched the toolchain. The riskiest assumptions (own surface host, Skia natives, in-place APK reads, lifecycle) are unproven.

Tasks

• Standalone net11.0-android app, outside the engine, on a pinned .NET 11 SDK
• SurfaceView + ANativeWindow_fromSurface + VK_KHR_android_surface via Silk.NET.Vulkan; clear plus one textured quad using Turian's SPIR-V
• Load SkiaSharp Android natives and draw text into a texture
• Read an uncompressed asset with AssetManager.OpenFd and its start offset
• Background/resume and rotation with surface destroy/recreate on a dedicated render thread
• Record the working toolchain combination (.NET SDK, workload, Android SDK platform, build-tools, JDK)
• Fall back to net10.0-android + Mono only on a concrete, documented blocker

Acceptance Criteria

• Runs on the Galaxy S24 FE and survives 20 background/resume cycles
• Toolchain versions recorded in the plan
• Findings note listing what phase B must handle

Related

• Android plan task A2 · seniority Sr · local-only on feat/android-platform until .NET 11 GA and CI support
• Depends on: Android: capture the Galaxy S24 FE Vulkan and device capabilities #234
• Platform roadmap: Platform roadmap research: Steam Deck, Android, iOS, Web #100