FoundationModelsBridge

Real actual: Apple Foundation Models, reached via a Swift class conforming to NativeLlm and registered into FoundationModelsBridge at app startup — see ai/ios-bridge/README.md. Kotlin/Native has no platform.FoundationModels.* cinterop binding (the framework's Swift-macro-driven @Generable/streamResponse surface has no ObjC-compatible shape), so this follows the same bridge mechanism Doori already shipped for FoundationModelsAnalyzer/ FoundationModelsLlmGateway: export a plain Kotlin interface to Swift as an ObjC protocol, implement it in Swift, inject the implementation through a top-level singleton at startup.

Until a consumer's AppDelegate sets FoundationModelsBridge.seam's generator, every method here degrades honestly (unavailable / NotSupportedOnPlatform / an empty stream) rather than crashing or faking success — the same behavior this class had as a hard stub, now driven by whether a bridge was actually registered instead of being permanently hardcoded.