docs(leap-sdk): refresh through v0.10.7 + SDK doc QA pass (DOC-27, DOC-37..DOC-60) by iamstuffed · Pull Request #97 · Liquid4All/docs

iamstuffed · 2026-05-15T17:41:18Z

Summary

What started as the v0.10.6 Android SDK QA fix list (DOC-27, DOC-37..DOC-60) grew into a multi-pass audit pipeline that surfaced and fixed three additional rounds of issues. Final scope:

Original Linear QA pass — 25 Android-SDK tickets, 41 numbered findings, verified against leap-android-sdk@cac3d06 (v0.10.6).
Critical-review audit pass — fanned out 7 parallel source-grounded audit agents across 14 SDK reference pages + 5 Android examples; found 70+ additional issues (fabricated Swift declarations, wrong Swift labels, broken Kotlin annotations, missing @Serializable, fake APIs, wrong V0.10.x version pin, false Mac Catalyst slice, no-JVM-target-jvm-target claim, etc.).
v0.10.7 docs refresh — release shipped 2026-05-18 (KMP HEAD 98a7c46). New leap-openai-client JVM + wasmJs targets; bytecode-hardening pass pinning all *-jvm artifacts to Java 11.
Artifact verification — actually downloaded the Maven Central JARs/AARs and the GitHub Release SPM XCFramework zips, inspected bytecode majors and framework headers, cross-checked every doc claim against the produced artifact. Found four real bugs (stale SPM checksums, Mac Catalyst false claim, Swift PascalCase mismatch, nested-class Swift name flattening).
Re-audit against v0.10.7 source — final source-grounded sweep. Found and fixed five more compile-broken code blocks (missing Swift convenience inits, broken nested code fence, SKIE-absence violations).

30 commits, 20 files, +861 / −546.

Section 1 — Original Linear QA (commits `3fa1aeb` → `6650914`)

Commit	Page	Tickets
`3fa1aeb`	`sdk/quick-start.mdx`	DOC-27, DOC-37, DOC-38, DOC-39
`3886345`	`sdk/model-loading.mdx`	DOC-40, DOC-41
`725a48b`	`sdk/ai-agent-usage-guide.mdx`	DOC-42, DOC-43
`7df6a53`	`sdk/conversation-generation.mdx`	DOC-44, DOC-60 (+ Swift `exportToJSON()` return type)
`8d4fdb8`	`sdk/messages-content.mdx`	DOC-45, DOC-46, DOC-47, DOC-48
`cfd77e7`	`sdk/constrained-generation.mdx`	DOC-49, DOC-50, DOC-60
`853bedd`	`sdk/voice-assistant.mdx`	DOC-51, DOC-52, DOC-53
`ddd8d0f`	`sdk/desktop-platforms.mdx`	DOC-54 (+ DOC-39 leak)
`6fe8e76`	`sdk/utilities.mdx`	DOC-55, DOC-56 (+ DOC-39, DOC-60, DOC-40 leaks)
`facb1a6`	`sdk/advanced-features.mdx`	DOC-57, DOC-58 (+ DOC-60 leak)
`dc43761`	`sdk/openai-client.mdx`	DOC-59
`5acf2d6`	`examples/android/*.mdx`	DOC-27, DOC-39, DOC-60 root causes
`b66e992`	drop `leap/edge-sdk/overview.mdx`	(legacy stub blocking `/leap/edge-sdk/overview` redirect)
`8bec74b`	`advanced-features` audit follow-up	DOC-49, DOC-50 (`JSONSchemaGenerator` / `GeneratableFactory` reference signatures)
`1f85c36`	`vision-language-model-example` audit follow-up	DOC-48 (JPEG, not PNG — `Image(ByteArray)` ctor hard-codes `data:image/jpeg;base64,…`)
`9c369c7`	batched cleanup across 12 files	aligns doc text with 0.10.6 source
`6650914`	`recipe-generator-constrained-output`	DOC-49, DOC-50 (import `Generatable`/`Guide` from `ai.liquid.leap.structuredoutput`)

Section 2 — Critical audit (commits `8a5f988` → `23cb977`)

After the QA pass shipped, ran a separate audit fanning out 7 source-grounded agents covering every SDK reference page + every Android example. Found 70+ issues across 16 files. Highlights:

constrained-generation.mdx — CityFact, Recipe, NutritionInfo missing @Serializable (would throw LeapGeneratableSchematizationException at runtime: JSONSchemaGenerator.kt:53-59); Swift setResponseFormat(type:) doesn't exist (canonical Swift path: options.with(jsonSchema: T.jsonSchema())); replaced 0.7-temperature default reference per project CLAUDE.md.
recipe-generator-constrained-output.mdx — @Generatable missing required description arg; @Guide placed on a class but @Target(AnnotationTarget.PROPERTY).
examples/android/leap-koog-agent.mdx — /tmp/models/ ADB path unreadable on Android (apps can't read /tmp/); switched to /data/local/tmp/liquid/ matching the other examples.
examples/android/vision-language-model-example.mdx — referenced nonexistent vlmModel.generateFromImage(image, prompt, maxTokens:); rewrote to use the real ImageUtils.fromBitmap(...) + Conversation.generateResponse pipeline. Model-name inconsistency (LFM2-VL vs LFM2.5-VL).
messages-content.mdx — fabricated Swift struct ChatMessage, enum ChatMessageContent, init(from: [String: Any]), ChatMessageRole: String. None exist — the iOS surface is the SKIE-bridged Kotlin types. Also: fromUIImage(image, compressionQuality:) doesn't take compressionQuality (hardcoded 0.85 in ChatMessageContentExtensionsIos.kt:24-29); no fromNSImage factory; Kotlin secondary ctor param is textContent, not text.
conversation-generation.mdx — Swift Conversation was shown as public class with private(set) var; it's a Kotlin interface bridged to a Swift protocol with { get } properties. AsyncThrowingStream<MessageResponse, Error> wrong (real type: SkieSwiftFlow<MessageResponse>). MessageResponse subclasses are data class, not class. LeapFunctionCallParserProtocol fabricated — real type is the abstract class LeapFunctionCallParser.
function-calling.mdx — Swift section invented an entire StringType / NumberType / ArrayType wrapper hierarchy that doesn't exist. Real names from LeapFunctionParameterType.kt:35-115: LeapStr/LeapNum/LeapInt/LeapBool/LeapArr/LeapObj/LeapNull. @ObjCName("functionDescription") / @ObjCName("parameterDescription") annotations on LeapFunction / LeapFunctionParameter mean the Swift label is functionDescription: / parameterDescription:, not description:.
voice-assistant.mdx — Swift AppleVoiceConversation: VoiceConversation protocol body declared with [Float] / Int32; the real LeapUi protocol uses LeapUi.KotlinFloatArray / LeapUi.KotlinInt (LeapUI and LeapSDK are separate frameworks with separate Kotlin runtimes, requiring an NSData bridge). Added the missing import android.os.Bundle in the Compose snippet. Fixed Float(fraction) cast (fraction is Kotlin Double).
utilities.mdx — fabricated LeapError.modelLoadingFailure / .generationFailure / .promptExceedContextLengthFailure / .serializationFailure. LeapError is a Swift typealias for the Kotlin open class LeapException; the real subclasses are LeapModelLoadingException, LeapGenerationException, etc. ChatMessage(from: json) initializer doesn't exist either.
advanced-features.mdx — LeapFunctionCallParserProtocol doesn't exist; setResponseFormat<T>(type:) throws doesn't exist (and JSONSchemaGenerator.getJSONSchema(for:) is non-throwing).
openai-client.mdx — leap-sdk-openai-client Kotlin module does NOT apply SKIE (verified at leap-sdk-openai-client/build.gradle.kts:3-11). The Swift example used for try await + onEnum(of:) which require SKIE. Also: stream = true is FORCED (OpenAiClient.kt:49 does request.copy(stream = true)), not a default. Added a Warning callout, rewrote the Swift section with a manual Flow.collect(...) + as? downcast pattern.
desktop-platforms.mdx — Mac Catalyst slice claim was false (Package.swift declares only .iOS(.v17) / .macOS(.v15); XCFramework Info.plist lists only 3 ARM64 slices). v0.10.2 was never published (the broken-version table was wrong about which versions exist). leap-openai-client-jvm artifact didn't exist at v0.10.6 (became true in v0.10.7 — see Section 3). JDK row corrected.

Section 3 — v0.10.7 docs refresh (commits `7c4394e`, `7073608`)

v0.10.7 published 2026-05-18; SPM tag d790011 built from leap-android-sdk@98a7c46 (PR Liquid4All/leap-android-sdk#256). New leap-openai-client slices for jvm (Ktor CIO) and wasmJs (Ktor Js). Bytecode hardening: all *-jvm and *-android artifacts now consistently emit class major 0x37 (Java 11) — they had silently been shipping Java 17/21 through v0.10.6. iOS surface unchanged.

Docs work:

Added v0.10.7 entry to leap-sdk-changelog.mdx, bumped "Latest release" header.
Restored a working JVM tab on openai-client.mdx (kept the SKIE-absence warning since SKIE is still off in v0.10.7).
Restored the JVM leap-openai-client dep line in desktop-platforms.mdx; reverted JDK row from 17 → 11 (matches the v0.10.7 bytecode pin).
Bumped version pins (Gradle coords, SPM download URLs, version-catalog values, nativelibs plugin version, Maven <version>) from 0.10.6 to 0.10.7 across 11 files. Preserved feature-introduction markers like (v0.10.6+) / since v0.10.6.
Added a "Coming in the next release" note under the openai-client SKIE warning naming the planned ergonomic improvements (for try await, onEnum(of:), nested-class Swift names, Swift convenience inits for OpenAiClientConfig).

Section 4 — Artifact verification (commit `20e3a61`)

After the v0.10.7 refresh, actually pulled every claimed artifact:

Maven Central probe — all 27 claimed artifacts return HTTP 200 at 0.10.7. leap-openai-client-jvm-0.10.7 and leap-openai-client-wasm-js-0.10.7 confirmed new (404 at every prior 0.10.x).
Bytecode hardening — unpacked 6 jars/AARs (leap-sdk-jvm, leap-openai-client-jvm, leap-ui-jvm, leap-sdk-android, leap-ui-android, leap-model-downloader-android); every representative .class entry shows cafe babe 0000 0037 = Java 11 major.
SPM XCFrameworks — downloaded all 4 zips from github.com/Liquid4All/leap-sdk/releases/download/v0.10.7/. Slice inventory exactly ios-arm64 / ios-arm64-simulator / macos-arm64 (no Catalyst, no Intel simulator).
LeapModelDownloader internals — v0.10.6 changes still present: @ObjCName(swiftName="ModelDownloader") rename, dual-import #error guard, dynamic Mach-O, bundled inference-engine dylibs under Frameworks/, re-exports LeapSDK Kotlin types.
LeapOpenAIClient SKIE absence — confirmed: no Modules/*.swiftmodule, no *-Swift.h, zero SkieSwiftFlow/onEnum hits (vs LeapSDK which has all of those).
KMP source at 98a7c46 — ChatMessage, LeapFunctionParameterType, @ObjCName labels, @Generatable/@Guide, root subprojects { ... JVM_11 } all verified.
Ktor engine claims — -jvm POM pulls ktor-client-cio-jvm, -android pulls ktor-client-okhttp-jvm, -wasm-js pulls ktor-client-js-wasm-js. All match docs.

Four real bugs found and fixed:

Stale SPM checksums in quick-start.mdx — the prior v0.10.7 commit bumped URLs but left v0.10.6 SHA-256 values. SPM would reject all four .binaryTarget pins. Replaced with the canonical hashes from leap-sdk@v0.10.7:Package.swift.
Mac Catalyst falsehood in quick-start.mdx (pre-existing since the initial 9dadc96 doc landing; the v0.10.6 audit caught it on desktop-platforms.mdx but missed quick-start.mdx).
Wrong Swift PascalCase — OpenAiClientKt.openAiClient(config:) should be OpenAiClientKt.OpenAiClient(config:) (Kotlin's PascalCase function name preserved through K/N).
Nested-class Swift names not flattened — ChatMessage.User / ChatCompletionEvent.Delta written in docs as if SKIE were on; without SKIE the K/N export flattens to ChatMessageUser / ChatCompletionEventDelta.

Section 5 — Re-audit (commit `bb19369`)

Final source-grounded sweep against leap-android-sdk@98a7c46. All 27 Leap imports across docs resolve to real source declarations; all kotlinx imports are standard. Five more bugs found in code blocks:

messages-content.mdx:108 — fromFloatSamples return type wrong (AudioPcmF32 → real Audio, WAV-encoded). Both the Swift overlay (ConvenienceExtensions.swift:550) and the Kotlin function (ChatMessageContentExtensions.kt:163,205) return ChatMessageContent.Audio. Reworded the surrounding prose to explain the Swift-vs-Kotlin asymmetry (Kotlin AudioPcmF32 is raw PCM; Swift fromFloatSamples re-encodes through WAV).
advanced-features.mdx:14 — broken nested code fence (outer ```swift wrapped prose + another inner ```swift). Fixed by dropping the outer fence.
openai-client.mdx (4 sites) — Swift OpenAiClient(config:) direct call doesn't compile without SKIE; corrected to OpenAiClientKt.OpenAiClient(config:) (top-level Kotlin fun OpenAiClient(config:) exports as <FileName>Kt.<funcName>). Also corrected line 269's "returns AsyncSequence<ChatCompletionEvent> (Swift)" claim — without SKIE it's the raw Kotlin Flow<ChatCompletionEvent>.
model-loading.mdx (3 sites) — LiquidInferenceEngineOptions(bundlePath:) 1-/2-/3-arg forms — none compile. The Swift overlay (ConvenienceExtensions.swift) has builder .with(...) methods but no convenience init; the K/N-generated designated init takes all 12 fields. Rewrote: steer Swift readers to the manifest variant (which DOES have a SKIE-bundled convenience init) and provide the verbose-but-correct 12-arg init for the sideloaded path.
model-loading.mdx:221 — JVM/native snippet used LeapDownloaderConfig(saveDir = cacheDir) with cacheDir ambiguous (page elsewhere binds it to a java.io.File). saveDir is String; replaced with a string literal + comment naming the Android conversion (context.cacheDir.absolutePath).

Test plan

npx mintlify dev from the worktree boots cleanly on every commit. No MDX parse errors.
All 17 SDK + example pages return HTTP 200 in dev preview at every checkpoint.
All 27 legacy URLs (10 /deployment/on-device/android/*, 10 /deployment/on-device/ios/*, plus :slug* wildcards and leap/edge-sdk/*) return 307 redirects to /deployment/on-device/sdk/*.
Every doc snippet cross-checked against leap-android-sdk source at the relevant commit (cac3d06 for v0.10.6 phase, 98a7c46 for v0.10.7 phase).
Imports, class kinds, ctor/method signatures, suspend modifiers, Gradle coordinates spot-verified across leap-sdk, leap-sdk-model-downloader, leap-sdk-openai-client, leap-ui.
Artifact verification: 27 Maven Central artifacts probed (all 200); 6 jar/AAR bytecode majors inspected (all 0x37 = Java 11); 4 SPM XCFramework zips downloaded from GitHub Releases and slice inventories verified.
SPM checksum sanity: all four .binaryTarget SHA-256 values in quick-start.mdx + desktop-platforms.mdx match the canonical values in leap-sdk@v0.10.7:Package.swift.
Reviewer to spot-check the Sections 2–5 commits (each is independently meaningful — 30 commits total, 20 files changed, +861 / −546). Per-page commits make review tractable.

Refs DOC-27, DOC-37, DOC-38, DOC-39, DOC-40, DOC-41, DOC-42, DOC-43, DOC-44, DOC-45, DOC-46, DOC-47, DOC-48, DOC-49, DOC-50, DOC-51, DOC-52, DOC-53, DOC-54, DOC-55, DOC-56, DOC-57, DOC-58, DOC-59, DOC-60.

mintlify · 2026-05-15T17:41:49Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
liquid-docs	🟢 Ready	View Preview	May 15, 2026, 5:42 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copilot

Pull request overview

This PR applies a comprehensive doc-QA pass across the Android (and cross-platform Kotlin) sections of the on-device SDK documentation against the v0.10.6 SDK release. It updates outdated import paths, replaces removed/renamed APIs in example snippets, corrects the Swift exportToJSON() return type, and removes a legacy leap/edge-sdk/overview.mdx stub that was blocking a redirect. Examples under examples/android/ are updated to match the same v0.10.6 API surface.

Changes:

Update Kotlin imports (model_downloader → downloader, top-level helpers → manifest package, MessageResponse from ai.liquid.leap → ai.liquid.leap.message) and replace removed ChatMessage.user(...) factory with the primary ChatMessage(role, ...) constructor across docs and examples.
Replace removed/renamed Kotlin APIs: setResponseFormatType(KClass) → reified setResponseFormatType<T>(); LeapModelDownloader constructor signature (drop extraHTTPRequestHeaders, add downloaderConfig/ioDispatcher, make request methods suspend, deprecate requestStopService); ChatMessageContent shape (Image(ImageUrl), Audio(InputAudio), removed toJSONObject/fromJSONObject in favor of kotlinx.serialization); LeapFunctionParameterType nested-class names now Leap-prefixed; getPromptTokensSize elevated to ModelRunner; Swift Conversation.exportToJSON() returns String (non-throwing).
Update voice-assistant snippet to send AudioPcmF32 directly instead of WAV re-encoding, and delete the legacy leap/edge-sdk/overview.mdx stub.

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
leap/edge-sdk/overview.mdx	Removes legacy stub so the `/leap/edge-sdk/overview` redirect can take effect.
examples/android/web-content-summarizer.mdx	Update downloader import and `ChatMessage` construction.
examples/android/vision-language-model-example.mdx	Update downloader import.
examples/android/slogan-generator.mdx	Update downloader import and `ChatMessage` construction.
examples/android/recipe-generator-constrained-output.mdx	Update downloader import, reified `setResponseFormatType`, primary `ChatMessage` ctor.
examples/android/leap-koog-agent.mdx	Update downloader import.
deployment/on-device/sdk/voice-assistant.mdx	Update downloader import, reorder/correct imports, send raw float32 PCM instead of WAV.
deployment/on-device/sdk/utilities.mdx	Swift `exportToJSON()` now returns `String`; updated Kotlin `LeapModelDownloader` reference signature, nested `ModelDownloadStatus`, suspend/deprecation notes; reified `setResponseFormatType` and primary `ChatMessage` ctor.
deployment/on-device/sdk/quick-start.mdx	Downloader package rename, notification field rename, manifest-package imports, primary `ChatMessage` ctor.
deployment/on-device/sdk/openai-client.mdx	Correct `MessageResponse` import path.
deployment/on-device/sdk/model-loading.mdx	Updated `LeapModelDownloader` reference signature; removed obsolete `ModelLoadingOptions.build`.
deployment/on-device/sdk/messages-content.mdx	New `ChatMessage` secondary ctor, switch from `JSONObject` helpers to `kotlinx.serialization`, new `ChatMessageContent` (`ImageUrl`/`InputAudio`) shape, `ImageUtils.fromBitmap` suspend helper.
deployment/on-device/sdk/desktop-platforms.mdx	Imports moved to `ai.liquid.leap.manifest`; primary `ChatMessage` ctor.
deployment/on-device/sdk/conversation-generation.mdx	Swift `exportToJSON()` returns `String`; remove Kotlin `exportToJSONArray` / non-reified `setResponseFormatType`; document `kotlinx.serialization` round-trip.
deployment/on-device/sdk/constrained-generation.mdx	Reified `setResponseFormatType`/`getJSONSchema`; switch JSON parsing to `kotlinx.serialization`; rename `createFromJSONObject` → `createFromJsonObject`.
deployment/on-device/sdk/ai-agent-usage-guide.mdx	Correct `MessageResponse` and `LeapModelDownloader` import paths.
deployment/on-device/sdk/advanced-features.mdx	Reified `setResponseFormatType`; renamed `LeapFunctionParameterType` nested classes (`LeapStr`, `LeapNum`, etc.); `getPromptTokensSize` now on `ModelRunner` and is `suspend`.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

…ction - `ai.liquid.leap.model_downloader.*` → `ai.liquid.leap.downloader.*` for `LeapModelDownloader` and `LeapModelDownloaderNotificationConfig` (DOC-27). - `notificationContentDownloading` → `notificationContentDownloadingTemplate` to match the real `LeapModelDownloaderNotificationConfig` field (DOC-37). - JVM section: `ai.liquid.leap.LeapDownloader{,Config}` → `ai.liquid.leap.manifest.LeapDownloader{,Config}` (DOC-38). - Replace 4× `ChatMessage.user(...)` (no such companion factory) with the real primary/secondary constructors (DOC-39). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk-model-downloader/src/androidMain/.../LeapModelDownloader.kt, LeapModelDownloaderNotificationConfig.kt, leap-sdk/src/commonMain/.../message/ChatMessage.kt, leap-sdk/src/commonMain/.../manifest/LeapDownloader.kt. Refs DOC-27, DOC-37, DOC-38, DOC-39.

…elLoadingOptions.build - Rewrite the Kotlin (Android) `LeapModelDownloader` class block to the real 5-parameter primary constructor: `(Context, File?, LeapModelDownloaderNotificationConfig, LeapDownloaderConfig, CoroutineDispatcher)`. The doc previously listed a 4-parameter signature with a nonexistent `extraHTTPRequestHeaders` field (DOC-40). - Drop the nonexistent `ModelLoadingOptions.Companion.build { ... }` factory from the Kotlin block and the example; switch the example to the direct primary-constructor form `ModelLoadingOptions(cpuThreads = 6, contextSize = 4096)`. `GenerationOptions.build {}` still exists and is unaffected; only `ModelLoadingOptions.build` was bogus (DOC-41). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk-model-downloader/src/androidMain/.../LeapModelDownloader.kt:56, leap-sdk/src/commonMain/.../ModelLoadingOptions.kt:6. Refs DOC-40, DOC-41.

… imports - `import ai.liquid.leap.MessageResponse` → `import ai.liquid.leap.message.MessageResponse` (DOC-43). - `import ai.liquid.leap.model_downloader.LeapModelDownloader` → `import ai.liquid.leap.downloader.LeapModelDownloader` (DOC-42). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../message/MessageResponse.kt, leap-sdk-model-downloader/src/androidMain/.../downloader/LeapModelDownloader.kt. Refs DOC-42, DOC-43.

…e-format API + Swift export return type - Drop the nonexistent `fun exportToJSONArray(): JSONArray` from the Kotlin `Conversation` interface block; switch the Kotlin "Export chat history" example to `kotlinx.serialization.encodeToString(conversation.history)` per the existing Utilities → Serialization pattern (DOC-44). - Drop the nonexistent `fun setResponseFormatType(kClass: KClass<*>)` overload from the documented `GenerationOptions` companion; switch the example to the real `inline fun <reified T> setResponseFormatType()` (DOC-60). Also fix a related bug not flagged by QA: Swift `Conversation.exportToJSON()` returns `String` (per `leap-sdk/src/appleMain/.../compat/ConversationExtensions.kt:45`), not `throws -> [[String: Any]]`. Updated the Swift interface block and Swift snippet accordingly. Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../Conversation.kt, leap-sdk/src/commonMain/.../GenerationOptions.kt:126, leap-sdk/src/appleMain/.../compat/ConversationExtensions.kt:45. Refs DOC-44, DOC-60.

… reference - Drop the nonexistent `ChatMessage.toJSONObject()` / `ChatMessage.Companion.fromJSONObject(obj)` from the Kotlin data-class block; point the Kotlin Serialization tab at `kotlinx.serialization.Json.encodeToString` / `decodeFromString` (DOC-45). - Rewrite the Kotlin `ChatMessageContent` reference block: it is a `sealed class`, not `sealed interface`; drop the nonexistent `fun clone()` / `fun toJSONObject()` members and the nonexistent top-level `ChatMessageContent.fromJSONObject(obj)` extension (DOC-46). - Replace the documented `Image(jpegByteArray: ByteArray)` / `Audio(wavByteArray: ByteArray)` primary constructors with the real `Image(imageUrl: ImageUrl)` / `Audio(inputAudio: InputAudio)` and call out the convenience secondary constructors plus the derived `jpegByteArray` / `data` properties (DOC-47). - Replace `ChatMessageContent.Image.fromBitmap(...)` (no such companion method) with the real Android-only `ai.liquid.leap.message.ImageUtils.fromBitmap(Bitmap, Int)` (note: `suspend`) (DOC-48). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../message/ChatMessage.kt:10, leap-sdk/src/commonMain/.../message/ChatMessageContent.kt:15, leap-sdk/src/androidMain/.../message/ImageUtils.kt. Refs DOC-45, DOC-46, DOC-47, DOC-48.

… APIs - `JSONSchemaGenerator.getJSONSchema(CityFact::class)` → `JSONSchemaGenerator.getJSONSchema<CityFact>()`. The real method has a reified-T form and a `KSerializer<T>` form — no `KClass` overload (DOC-49). - `GeneratableFactory.createFromJSONObject(JSONObject(jsonContent))` → `GeneratableFactory.createFromJsonObject<T>(kxObj)`. Two bugs in one line: method name uses camelCase `Json` (not `JSON`), and the argument is `kotlinx.serialization.json.JsonObject` (not `org.json.JSONObject`) (DOC-50). - `setResponseFormatType(CityFact::class)` → `setResponseFormatType<CityFact>()` (DOC-60). - Update the prose, "Apply the schema" example, the schema-injection helper, and the Best-Practices parser snippet to use the corrected APIs consistently. Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../structuredoutput/JSONSchemaGenerator.kt, leap-sdk/src/commonMain/.../structuredoutput/GeneratableFactory.kt, leap-sdk/src/commonMain/.../GenerationOptions.kt:126. Refs DOC-49, DOC-50, DOC-60.

…Pcm16Wav helper - `import ai.liquid.leap.MessageResponse` → `import ai.liquid.leap.message.MessageResponse` (DOC-51). - `import ai.liquid.leap.model_downloader.LeapModelDownloader` → `import ai.liquid.leap.downloader.LeapModelDownloader` (DOC-52). - Drop the import and call of `ai.liquid.leap.message.encodePcm16Wav(...)` — no such top-level function exists in v0.10.6. Switch the Kotlin `LeapVoiceConversation.generateResponse` example to `ChatMessageContent.AudioPcmF32(audioSamples, sampleRate)`, which skips the WAV re-encode entirely (DOC-53). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../message/MessageResponse.kt, leap-sdk-model-downloader/src/androidMain/.../downloader/LeapModelDownloader.kt, leap-sdk/src/commonMain/.../message/ChatMessageContent.kt (AudioPcmF32 variant), no occurrence of encodePcm16Wav in leap-sdk/src. Refs DOC-51, DOC-52, DOC-53.

- `ai.liquid.leap.LeapDownloader` → `ai.liquid.leap.manifest.LeapDownloader` (DOC-54, issue 25). - `ai.liquid.leap.LeapDownloaderConfig` → `ai.liquid.leap.manifest.LeapDownloaderConfig` (DOC-54, issue 26). - `ai.liquid.leap.ModelSource` → `ai.liquid.leap.manifest.ModelSource` (DOC-54, issue 27). - Replace `ChatMessage.user("What is the capital of France?")` (nonexistent companion factory — same as DOC-39) with `ChatMessage(ChatMessage.Role.USER, "What is the capital of France?")`. Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../manifest/LeapDownloader.kt, leap-sdk/src/commonMain/.../manifest/LeapDownloaderConfig.kt, leap-sdk/src/commonMain/.../manifest/ModelSource.kt, leap-sdk/src/commonMain/.../message/ChatMessage.kt. Refs DOC-54, DOC-39.

…nloadStatus - Rewrite the Kotlin status-polling block to match the real v0.10.6 surface: * `LeapModelDownloader` primary constructor has 5 parameters: `(Context, File?, LeapModelDownloaderNotificationConfig, LeapDownloaderConfig, CoroutineDispatcher)`. The previous block listed a nonexistent `extraHTTPRequestHeaders` field (same as DOC-40). * `requestDownloadModel` is `suspend` (DOC-55, issue 28). * `requestStopDownload` is `suspend` (DOC-55, issue 29). * `requestStopService` is `@Deprecated` *and* `suspend` (DOC-55, issue 30). * `ModelDownloadStatus` is nested under `LeapModelDownloader` — there is no top-level `ai.liquid.leap.downloader.ModelDownloadStatus` (DOC-56). - Update the bullet list under the block to reflect the new modifiers and deprecation. - Putting-it-together example: replace `setResponseFormatType(TripRecommendation::class)` with `setResponseFormatType<TripRecommendation>()` (DOC-60) and replace `ChatMessage.user(...)` with the real constructor (DOC-39). - Fix a related Swift bug not flagged by QA: `Conversation.exportToJSON()` returns `String`, not `throws -> [[String: Any]]` (per leap-sdk/src/appleMain/.../ConversationExtensions.kt:45). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk-model-downloader/src/androidMain/.../downloader/LeapModelDownloader.kt (lines 56, 268, 349, 374, 450, 501). Refs DOC-55, DOC-56, DOC-39, DOC-60.

…nd drop bogus runner cast - Rewrite the Kotlin `LeapFunctionParameterType` nested classes to the real names with a `Leap` prefix — `LeapStr`, `LeapNum`, `LeapInt`, `LeapBool`, `LeapNull`, `LeapArr`, `LeapObj`. The prefix exists upstream specifically to avoid shadowing `kotlin.String`, `kotlin.Number`, etc., and the Function Calling guide on the adjacent page already uses these names (DOC-57, issues 32–38). - Remove the `runner as? LiquidInferenceEngineRunner` cast around `getPromptTokensSize`. `getPromptTokensSize(messages:, addBosToken:)` is declared directly on the cross-platform `ModelRunner` interface in v0.10.6, so no cast is needed. `LiquidInferenceEngineRunner` only exists as an Apple compat class at `ai.liquid.leap.compat.LiquidInferenceEngineRunner` — there is no `ai.liquid.leap.LiquidInferenceEngineRunner`, and on Kotlin Android the cast was always unresolved (DOC-58). - Drop the nonexistent `fun setResponseFormatType(kClass: KClass<*>)` overload from the documented Kotlin `GenerationOptions` companion; the only real method is `inline fun <reified T> setResponseFormatType()` (DOC-60). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../function/LeapFunctionParameterType.kt, leap-sdk/src/commonMain/.../ModelRunner.kt:39, leap-sdk/src/commonMain/.../GenerationOptions.kt:126, leap-sdk/src/appleMain/.../compat/LiquidInferenceEngineRunner.kt. Refs DOC-57, DOC-58.

- `import ai.liquid.leap.MessageResponse` → `import ai.liquid.leap.message.MessageResponse` in the hybrid on-device + cloud routing Kotlin (Android) snippet. Real package is `ai.liquid.leap.message`, same as DOC-43 and DOC-51 on other pages (DOC-59). Verified against leap-android-sdk v0.10.6 (commit cac3d06): leap-sdk/src/commonMain/.../message/MessageResponse.kt. Refs DOC-59.

…mple pages The example pages under examples/android/ had the same outdated patterns flagged by the QA pass on the SDK reference pages: - Wrong import package `ai.liquid.leap.model_downloader.LeapModelDownloader` → `ai.liquid.leap.downloader.LeapModelDownloader` across all 5 files (DOC-27 root cause). - `setResponseFormatType(Recipe::class)` → `setResponseFormatType<Recipe>()` plus the matching prose mention in recipe-generator-constrained-output.mdx (DOC-60 root cause). - `ChatMessage.user(prompt)` → `ChatMessage(ChatMessage.Role.USER, prompt)` across recipe-generator-constrained-output, slogan-generator, and web-content-summarizer (DOC-39 root cause). Verified against leap-android-sdk v0.10.6 (commit cac3d06). Refs DOC-27, DOC-39, DOC-60.

…ct fires The file at leap/edge-sdk/overview.mdx was a leftover from the pre-unification "LEAP Edge SDK" page tree. docs.json already redirects `/leap/edge-sdk/overview` → `/deployment/on-device/sdk/quick-start`, but Mintlify prefers existing files over redirect rules, so the legacy page kept rendering with broken internal links (e.g. `./ios/ios-quick-start-guide`). Removing the file lets the redirect fire. Verified with `npx mintlify dev` after deletion: GET /leap/edge-sdk/overview → 307 /deployment/on-device/sdk/quick-start. All 27 previously-known-good legacy URLs (10 android/, 10 ios/, plus :slug* wildcards and the Edge SDK paths) now return 3xx redirects to the unified /deployment/on-device/sdk/* tree.

…leFactory reference signatures Audit follow-up. The reference signature blocks for `JSONSchemaGenerator` and `GeneratableFactory` in this page still showed the pre-v0.10.6 surface — a `KClass` overload for both, and `JSONObject` (the `org.json` type) on the factory. Real signatures (verified against `leap-sdk/src/commonMain/.../structuredoutput/JSONSchemaGenerator.kt` and `GeneratableFactory.kt`): - `JSONSchemaGenerator.getJSONSchema(serializer: KSerializer<T>, indentSpaces: Int? = null): String` plus the reified-T form. No `KClass` overload. - `GeneratableFactory.createFromJsonObject(jsonObject: kotlinx.serialization.json.JsonObject, serializer: KSerializer<T>): T` plus the reified-T form. Note camelCase `Json` in the method name and the `kotlinx.serialization.json.JsonObject` argument (not `org.json.JSONObject`). The working code snippets on this page and on `constrained-generation.mdx` already use the correct reified syntax — only the reference tables were stale. Same root cause as DOC-49 and DOC-50; tightening the reference signatures so they match the example usage. Refs DOC-49, DOC-50.

`ChatMessageContent.Image(jpegByteArray: ByteArray)` is a convenience secondary constructor that wraps the bytes in a `data:image/jpeg;base64,...` URL (see `leap-sdk/src/commonMain/.../message/ChatMessageContent.kt` — `JPEG_BASE64_DATA_URL_PREFIX` is hard-coded). Passing PNG bytes still compiles but produces a content-type mismatch on the wire that the model will reject or misinterpret. Switch the example to `ImageUtils.fromBitmap(bitmap, compressionQuality = 85)` — the canonical Android helper, which JPEG-encodes via `Bitmap.compress(JPEG, ...)` on `Dispatchers.Default` and returns a `ChatMessageContent.Image` ready to send. Drop the now-unused `ByteArrayOutputStream` import. Refs DOC-48.

…redoutput package @Generatable and @Guide are declared in ai.liquid.leap.structuredoutput (Annotations.kt) and are not re-exported from the top-level ai.liquid.leap package. Copy-pasting the original snippet failed with 'unresolved reference'. Refs DOC-49/50, DOC-60.

@serializable

…ated Swift APIs JSONSchemaGenerator throws LeapGeneratableSchematizationException("Type must be @serializable to generate JSON Schema") when the type lacks @serializable (leap-sdk/src/commonMain/.../JSONSchemaGenerator.kt:53-59), so the CityFact, Recipe, and NutritionInfo snippets were runtime-broken. @Generatable requires a description (no Kotlin default) and @Guide is @target(AnnotationTarget.PROPERTY) only (Annotations.kt:14,21), so the recipe-generator example with class-level @Guide and no @Generatable description was compile-broken. Also corrects the Swift side: setResponseFormat(type:) does not exist (canonical path is options.with(jsonSchema: T.jsonSchema()), or GenerationOptionsCompat.setResponseFormat(jsonSchema:)), JSONSchemaGenerator.getJSONSchema(for:) is non-throwing (no try), and LeapSDKMacros must be imported alongside LeapModelDownloader. Replaces the "computed via reflection" claim with the actual mechanism (kotlinx.serialization descriptor) and drops the misleading 0.7 default-temperature reference per project CLAUDE.md guidance.

…cated VLM API leap-koog-agent: Apps cannot read /tmp/ on Android — switch the ADB commands and modelPath to /data/local/tmp/liquid/ (matches recipe-generator and VLM example). Drop the inconsistent .bundle filename reference; the SDK ships GGUFs. vision-language-model-example: the page mixed LFM2-VL-1.6B and LFM2.5-VL-1.6B — unify on LFM2.5-VL-1.6B (matches the actual ModelSource(modelName: "LFM2.5-VL-1.6B") load call). Replace the askQuestionAboutImage snippet that called the nonexistent vlmModel.generateFromImage(image, prompt, maxTokens:) with the real ImageUtils.fromBitmap + Conversation.generateResponse pipeline. Rewrite the lifecycle section to call ModelRunner.unload() (suspend) with a re-entrance guard instead of the made-up releaseModel()/initializeModel() pair.

…Swift factory APIs quick-start: MessageResponse.ReasoningChunk has `reasoning`, not `text` (MessageResponse.kt:50). The previous Kotlin snippet would not compile. Also replace nonexistent Swift .image(jpegData) / .audio(wavData) positional factories with the real ChatMessageContent.fromJPEGData(_:) / .fromWAVData(_:) (ChatMessageContentExtensions.swift:14-58), pass reasoningContent: / functionCalls: explicitly (Kotlin defaults do not propagate through K/N), and steer the Swift GenerationOptions snippet to the canonical parameterless init + .with(...) builder chain. model-loading: DownloadedModelManifest.manifest is typed as Manifest, not ModelManifest (Manifest.kt:30). LiquidInferenceEngineOptions.bundlePath is declared `val`, so the Swift surface is `let`, not `var`. SamplingParameters includes a topK field that was missing from the snippet. Drop the misleading "evictUnusedModel is a no-op" reference — that method is private to the service process and not part of any public API.

…t and Content enum The Swift API is generated by Kotlin/Native + SKIE from the Kotlin types — there is no native Swift `struct ChatMessage`, no `enum ChatMessageContent`, no `ChatMessageRole: String` with raw values, and no `init(from: [String: Any])` on either type. Replace those fabrications with the real bridged-class surface where Kotlin parameter defaults do not propagate (init requires all four args) and the role enum is ChatMessage.Role (no String raw-value backing). Drop the nonexistent ChatMessageContent.fromUIImage(image, compressionQuality:) (JPEG quality is hardcoded to 0.85 in the iOS overlay) and the entirely fictitious fromNSImage helper. Replace .audio(wavData) positional factory calls with the real ChatMessageContent.fromWAVData(_:). Fix the Kotlin secondary constructor parameter name (textContent, not text) per ChatMessage.kt:74-77, and add the nested ImageUrl/InputAudio types + toWavBytes()/toAudio() helpers that were missing. Also corrects the prose: ChatMessageContent is a sealed class, not a sealed interface; LeapSerializationException, not LeapSerializationError.

… + SKIE export Conversation is a Kotlin interface bridged to Swift as a protocol with `{ get }` properties, not a Swift class with `let` / `private(set) var`. Swift parameter labels match the Kotlin parameter names (`function:`, `functions:`, `message:`) — there are no underscore-labeled `_ function:` / `_ message:` overloads. Generation methods return `SkieSwiftFlow<MessageResponse>` (iterable with `for try await`), not `AsyncThrowingStream<MessageResponse, Error>`. Drop the "Swift only" qualifier on `functions` — the property is on the Kotlin Conversation interface (Conversation.kt:25), available on every platform. Change every MessageResponse sealed subtype to `data class` (MessageResponse.kt:41-83) so equals/hashCode/copy semantics survive. `GenerationStats.tokenPerSecond` is non-nullable Float; only the parent `stats: GenerationStats?` is nullable. Replace the fabricated Swift `setResponseFormat<T>(type:)` and `LeapFunctionCallParserProtocol` types with the real canonical paths (builder `.with(jsonSchema:)` and the LeapFunctionCallParser class — there is no Protocol suffix). Switch GenerationOptions Swift examples from the partial kwarg init (which doesn't exist because Kotlin defaults don't propagate) to the parameterless init + `.with(...)` builder chain from ConvenienceExtensions.swift.

utilities: LeapError is a typealias for LeapException (Kotlin open class), not a Swift enum — replace fabricated cases (.modelLoadingFailure, .generationFailure, .promptExceedContextLengthFailure, .serializationFailure) with the real LeapException subclass names (LeapException.kt:21-38). Drop the nonexistent onErrorCallback reference and the fictitious ChatMessage(from: [String: Any]) initializer. Note that ModelDownloadStatus nesting differs by platform (Android: nested under LeapModelDownloader; Apple: top-level with a different payload — DownloadInProgress(progress: Double) vs the Android variant). Fix LeapDownloaderConfig.saveDir which takes a String, not a File (so cacheDir needs .absolutePath on Android). Replace the partial-args Swift GenerationOptions init + setResponseFormat(type:) with the builder + jsonSchema form. advanced-features: LeapFunctionCallParserProtocol does not exist — the type is the abstract Kotlin class LeapFunctionCallParser, bridged to Swift as a class with the same name. Remove the fabricated mutating setResponseFormat<T>(type:) — Swift schema setting goes through .with(jsonSchema: T.jsonSchema()) (or GenerationOptionsCompat). Steer the Swift GenerationOptions snippet to the parameterless init + chained .with(...) builders rather than a full-arg init that would require all 13 fields. Add the LeapSDKMacros import for JSONSchemaGenerator and drop the non-throwing-method `try`. Replace the parser-implementation prose with "subclass" since LeapFunctionCallParser is an abstract class on both platforms.

…e Swift labels LeapFunction and LeapFunctionParameter both carry @ObjCName annotations on their description parameters (LeapFunction.kt:19, LeapFunctionParameter at line 71), so the Swift initializer labels are functionDescription: and parameterDescription:, not description:. LeapFunctionParameter.optional has no Swift default — pass optional: false for required parameters (Kotlin defaults don't propagate through K/N + ObjC). The previously documented Swift API (.string(StringType()), .number(NumberType()), .array(ArrayType(...)), .null(NullType) plus their wrapper types) is entirely fabricated. The real Swift surface preserves the Kotlin nested-class names from LeapFunctionParameterType.kt:35-115: LeapFunctionParameterType.LeapStr(enumValues:description:), .LeapNum(enumValues:description:), .LeapInt(enumValues:description:), .LeapBool(description:), .LeapArr(itemType:description:), .LeapObj(properties:required:description:), .LeapNull() (no description). SKIE does NOT generate cleaner .string(...) / .number(...) aliases — the "Swift bindings expose the same primitives under cleaner names" claim was wrong. Rewrites every Swift snippet in the page to use the real class names plus ObjCName-renamed labels, and corrects the LeapFunctionCall.arguments type to [String: Any] (the ObjC bridge collapses Kotlin Any? to non-optional id).

…nce and pin ai-agent-usage-guide: Swift's stdlib has no asyncMap — rewrite the agent loop's tool-execution pass as a sequential `for await` accumulation. Fix the missing `workingConv.` prefix on the Kotlin modelRunner reference (Conversation.kt:16 declares `val modelRunner: ModelRunner` on the interface). Replace .image(jpegData) / .audio(wavData) positional factories with the real ChatMessageContent.fromJPEGData(_:) / .fromWAVData(_:). Add the missing reasoningContent: nil / functionCalls: nil args on every Swift ChatMessage call. Switch the Swift GenerationOptions call to the builder chain. Correct the Kotlin/Native version pin: only v0.10.0, v0.10.1, and v0.10.6 exist on the android-sdk repo (v0.10.2 and v0.10.3 were never tagged); fixes shipped via v0.10.4.x on the SPM repo and v0.10.6 on the android-sdk repo. Pin to 0.10.6 or newer. Annotate the audio.samples access with a note that it's a KotlinFloatArray (needs the floatArrayToNSData bridge before passing to a [Float]-typed renderer). voice-assistant: fraction in downloadProgress is Kotlin Double — cast to Float before passing to setModelProgress(fraction: Float, ...). Add the missing `import android.os.Bundle` to the Compose snippet. Rewrite the AppleVoiceConversation Swift adapter to actually conform to the protocol — the LeapUI VoiceConversation protocol method takes LeapUi.KotlinFloatArray / LeapUi.KotlinInt (the LeapUI and LeapSDK frameworks have separate Kotlin runtimes; cross-framework Kotlin types do not interconvert without an NSData bridge). Add the missing systemPrompt: nil in the Swift modelRunner.createConversation() call (no Swift default). Correct the Compose "transitively" claim — leap-ui depends on Compose with implementation scope, so the runtime artifacts are pulled in but the APIs are not re-exported.

…Swift API openai-client: the leap-sdk-openai-client Kotlin module does NOT apply the SKIE plugin (verified in leap-sdk-openai-client/build.gradle.kts:3-11 — only leap-sdk, leap-sdk-model-downloader, and leap-ui do), so Flow<ChatCompletionEvent> is not bridged to Swift AsyncSequence and onEnum(of:) is not generated for ChatCompletionEvent. The "for try await event in client.streamChatCompletion(...)" + "switch onEnum(of: event)" Swift example would not compile. Rewrite the Swift section with a Warning callout explaining the SKIE absence and a manual Flow.collect(collector: FlowCollector { ... }) + `as?` downcast pattern. Also corrects the streaming claim: streamChatCompletion(...) forces request.copy(stream = true) on the outgoing payload (OpenAiClient.kt:49), overriding whatever stream field the caller set — not a default. Drop the JVM artifact claim entirely: leap-sdk-openai-client/build.gradle.kts declares no jvm() target, and Maven Central confirms no leap-openai-client-jvm artifact exists (https://repo1.maven.org/maven2/ai/liquid/leap/leap-openai-client-jvm/ returns 404). For JVM-only hosts, recommend a standard OpenAI Java/Kotlin SDK. desktop-platforms: same JVM-artifact correction (drop the commented `// implementation("ai.liquid.leap:leap-openai-client:0.10.6")` from the JVM example). Correct the JDK row: leap-sdk's jvm() target inherits kotlin.jvmToolchain(17) — JDK 11 only applies to the Android target. Correct the broken-version block: v0.10.2 was never published (only v0.10.0, v0.10.1, and v0.10.6 on the android-sdk repo); fixes shipped across v0.10.4.x on the SPM repo and v0.10.6 on the android-sdk repo. Pin to v0.10.6 or newer. Drop the false Mac Catalyst claim — the released LeapSDK.xcframework slices are only ios-arm64, ios-arm64-simulator, and macos-arm64. Add a note that the simulator slice is ARM64-only (no Intel-Mac simulator support). Fix the mmap-default changelog anchor (#memory-mapped-model-loading-by-default). cloud-ai-comparison: correct `MessageResponse.functionCalls` to `MessageResponse.FunctionCalls` (the sealed-variant name, not a property). Replace the fabricated `GenerationOptions.setResponseFormat(type:)` cell with the real per-platform helpers (Swift options.with(jsonSchema: T.jsonSchema()), Kotlin setResponseFormatType<T>()). Fix the streaming-response cell to name the real Swift type (SkieSwiftFlow<MessageResponse>, iterable with `for try await`) instead of AsyncThrowingStream. Switch the role-tagged message example to ChatMessage(role:textContent:) to avoid the 4-arg content-list form.

v0.10.7 closes the JVM gap on leap-openai-client — the module now publishes `jvm` (Ktor CIO) and `wasmJs` (Ktor Js) targets alongside the prior android / apple / linux / mingw slices (PR Liquid4All/leap-android-sdk#256). Bytecode across all -jvm artifacts is now uniformly Java 11 (was silently 17 / 21 through v0.10.6). iOS Swift surface unchanged from v0.10.6. Docs changes: - leap-sdk-changelog: add v0.10.7 entry, bump "Latest release" header. - openai-client: replace the K/N-only Gradle tab with a JVM tab plus a separate Kotlin/Native tab; drop the audit-era "no JVM target" warning but keep the SKIE-absence warning (SKIE is still not applied to the openai-client module in v0.10.7). - desktop-platforms: restore the leap-openai-client JVM dependency in the Gradle snippet; revert JDK row to JDK 11 (matches the v0.10.7 bytecode hardening); extend the K/N broken-version warning to cite v0.10.7 in the fix cascade. - voice-assistant: reword the Wasm-preview disclaimer from "v0.10.6 release notes" to "through v0.10.7" — Wasm is still preview-only. - Bump version pins (Gradle coords, SPM download URLs, version catalog values, nativelibs plugin version, Maven <version>, recipe-generator step) from 0.10.6 to 0.10.7. Preserved feature-introduction markers ("v0.10.6+", "since v0.10.6", etc.) — those still point at the version that introduced the feature.

Verified every doc claim against the actual published artifacts (Maven Central + GitHub Releases SPM zips + leap-android-sdk@98a7c46 source). Four real bugs surfaced and fixed: 1. **Stale SPM checksums.** Bulk-bumping the SPM download URLs from v0.10.6 to v0.10.7 in the prior commit didn't update the SHA-256 values next to them. SPM would reject all four .binaryTarget pins. Replaced with verified v0.10.7 SHA-256 (cross-checked against leap-sdk@v0.10.7:Package.swift and local shasum -a 256 of each downloaded XCFramework zip). 2. **Mac Catalyst claim removed from quick-start.** The doc has said "Mac Catalyst 17.0+ also supported" since the initial 9dadc96 docs landing (PR #94). The desktop-platforms audit caught the same falsehood there, but quick-start was missed until artifact verification — Package.swift declares only .iOS(.v17) and .macOS(.v15); every shipped XCFramework Info.plist lists exactly ios-arm64 / ios-arm64-simulator / macos-arm64 LibraryIdentifiers (no maccatalyst slice). Rewrote line to say ARM64-only explicitly and cite the slice inventory. 3. **Wrong Swift function-name case in openai-client.** Docs said `OpenAiClientKt.openAiClient(config:)`. The actual Swift name from K/N export is `OpenAiClientKt.OpenAiClient(config:)` (capital O — Kotlin's PascalCase top-level fun name is preserved). Verified against LeapOpenAIClient.framework/Headers/LeapOpenAIClient.h line 494: `OpenAiClientConfig:(...) swift_name("OpenAiClient(config:)")`. 4. **Nested-class Swift names in openai-client.** Without SKIE applied to the openai-client module, K/N flattens nested classes — they are NOT exposed as `ChatMessage.User` / `ChatCompletionEvent.Delta` in Swift, but as `ChatMessageUser` / `ChatCompletionEventDelta`. Verified against the framework header swift_name attributes at lines 285 (ChatMessageAssistant), 304 (ChatMessageSystem), 323 (ChatMessageUser), 157 (ChatCompletionEventDelta), 176 (ChatCompletionEventDone), 195 (ChatCompletionEventError). Updated both the basic-usage Swift example and the hybrid-routing ViewModel snippet. Added an inline note explaining the flattening so readers know to apply the same pattern to other Kotlin nested types if they extend the example. Verification footprint that produced these findings: - Maven Central probe: 27 artifacts at 0.10.7 (all 200, including new leap-openai-client-{jvm,wasm-js}) - 6 jars unpacked: bytecode major = 0x37 (Java 11) across leap-sdk-jvm, leap-openai-client-jvm, leap-ui-jvm, leap-sdk-android, leap-ui-android, leap-model-downloader-android - 4 XCFramework zips downloaded from github.com/Liquid4All/leap-sdk/releases/download/v0.10.7/: all 3 documented slices, no Catalyst, no Intel simulator - LeapModelDownloader.framework verified: @ObjCName(swiftName= "ModelDownloader"), dual-import #error guard, dynamic Mach-O, bundled inference-engine dylibs under Frameworks/, re-exports LeapSDK Kotlin types (4 swift_name hits for Conversation / ModelRunner / ChatMessage / GenerationOptions) - LeapOpenAIClient.framework verified: SKIE absent (no Modules/*.swiftmodule, no Headers/*-Swift.h, zero SkieSwiftFlow / onEnum hits; LeapSDK has those by contrast) - KMP source at 98a7c46 verified: ChatMessage primary ctor unchanged (4 fields), LeapFunctionParameterType subclasses unchanged (LeapStr/LeapNum/LeapInt/LeapBool/LeapArr/LeapObj/LeapNull), @ObjCName labels on LeapFunction line 19 / 71, root build.gradle.kts:128-152 centralizes JvmTarget.JVM_11 in subprojects {}, openai-client build still has no skie plugin - POM dependency check: leap-openai-client-jvm pulls ktor-client-cio-jvm (matches "CIO Ktor engine" claim), -android pulls ktor-client-okhttp-jvm (matches "OkHttp-engine Ktor client" claim), -wasm-js pulls ktor-client-js-wasm-js (matches "Ktor Js engine" claim) - Historical pin check: leap-openai-client-jvm and -wasm-js are 404 at every prior 0.10.x release (0.10.0 through 0.10.6) — "landed in v0.10.7" framing in the changelog is correct

…next release The current SKIE-absence warning told Swift readers what to do today (manual Flow.collect + as? downcast, flattened ChatMessageUser / ChatCompletionEventDelta type names) but didn't signal that this is transitional. Add a 'Coming in the next release' bullet under the warning callout in openai-client.mdx and a sentence in the v0.10.7 changelog entry naming the planned changes: - for try await over streamChatCompletion(...) - onEnum(of: event) exhaustive switching - Nested-class Swift names (ChatCompletionEvent.Delta) instead of the current flattened form (ChatCompletionEventDelta) - Swift convenience inits / builders for OpenAiClientConfig Frame it as 'pin to v0.10.7 if you need the current behavior frozen, otherwise expect the more ergonomic surface to land soon' so readers copy-pasting today's manual-collector code know it'll work but isn't the long-term shape.

…v0.10.7 Re-ran the audit against leap-android-sdk @ 98a7c46 (v0.10.7) focused on imports and code-block correctness. All 27 Leap imports across the docs resolve to real source declarations. Four real bugs surfaced: 1. **messages-content.mdx:108** — Swift static factory return type was stated as `ChatMessageContent.AudioPcmF32` but both the Swift overlay (ConvenienceExtensions.swift:546-562) and the underlying Kotlin function (ChatMessageContentExtensions.kt:159-188) return `ChatMessageContent.Audio` (WAV-encoded via FloatAudioBuffer.makeAudioContent). Fixed return type and rewrote the surrounding prose to call out the Swift-vs-Kotlin asymmetry: Kotlin AudioPcmF32 is raw PCM; Swift fromFloatSamples re-encodes through WAV. 2. **advanced-features.mdx:14** — Broken nested code fence. The Swift tab opened ```swift, then included prose, then opened ANOTHER ```swift for the actual code. Prose rendered as Swift source. Dropped the outer opener so prose is markdown and the inner fence is the only code block. 3. **openai-client.mdx (4 sites)** — The leap-sdk-openai-client module does NOT apply SKIE (verified earlier; still true at 98a7c46), so the top-level Kotlin `fun OpenAiClient(config:)` factory is exported as Swift `OpenAiClientKt.OpenAiClient(config:)`. The OpenRouter (line 184), self-hosted vLLM (line 217), and lifecycle prose (411, 419) all referenced `OpenAiClient(config:)` as if it were a direct Swift initializer. Fixed to use the actual K/N-exported path `OpenAiClientKt.OpenAiClient(config:)` with an inline comment pointing back to the SKIE-absence warning. Also corrected line 269's response-shape claim: `streamChatCompletion(request)` returns a Kotlin `Flow<ChatCompletionEvent>` — without SKIE on this module, it is NOT bridged to a Swift `AsyncSequence` in v0.10.7. 4. **model-loading.mdx (3 sites)** — `LiquidInferenceEngineOptions` ships no Swift convenience init in v0.10.7: the only entry point is the K/N-generated 12-arg designated init from Kotlin's data class (LiquidInferenceEngineOptions.kt:74-114). Verified directly against the downloaded XCFramework header (`init(bundlePath:cacheOptions:cpuThreads: contextSize:nGpuLayers:mmProjPath:audioDecoderPath:chatTemplate: audioTokenizerPath:audioDecoderUseGpu:useMmap:extras:)`). The legacy accordion's `LiquidInferenceEngineOptions(bundlePath: ggufURL.path, mmProjPath: mmprojURL.path)` (2-arg) and the tuning section's 3-arg / single-arg + .with(...) chain forms all fail to compile. Rewrote: - Legacy accordion: shows `Leap.load(url:)` (simple case) and the verbose-but-correct 12-arg `LiquidInferenceEngineOptions(...)` for companion-path overrides, with an explicit note about the K/N defaults-don't-propagate constraint. - Tuning section: steers Swift readers to the manifest variant (`LiquidInferenceEngineManifestOptions` HAS a SKIE-bundled convenience init at ConvenienceExtensions.swift:397-415), shows its `.with(...)` chain, and explicitly calls out that the non-manifest `LiquidInferenceEngineOptions` has no Swift shortcut today and `.with(...)` requires a fully-built starting instance. 5. **model-loading.mdx:221** — JVM/native snippet used `LeapDownloaderConfig(saveDir = cacheDir)` with an undeclared `cacheDir`. `saveDir` is `String` (not `File`); the page elsewhere binds `cacheDir` to a `java.io.File` in an Android context, so copy-paste readers would hit a type mismatch. Switched to a string literal with a comment naming the Android conversion (`context.cacheDir.absolutePath`).

Adds a positioning section at the top of the page that calls out Leap as Liquid AI's official on-device inference SDK with first-class support for Liquid Foundation Models (LFM2, LFM2.5, LFM2.5-Audio, LFM2.5-VL). The 'What "first-class support" gets you' subsection ties the positioning to concrete, source-verifiable benefits: day-one model coverage, validated per-checkpoint sampler defaults (bundle manifest), LFM-native chat templates and function-call dialect parsers, multimodal LFMs in one API, end-to-end constrained generation, and one-call model fetching from the LEAP Model Library. A separate 'Other features' subsection keeps the non-Liquid-specific bullets (on-device, KV cache, mmap, hybrid routing, voice UI). Preserves the existing 0.9.x migration Info callout (now placed below the new intro) and the rest of the page unchanged.

Move the 'What is the Leap SDK?' intro that landed inline in quick-start into its own first-in-sidebar page under the Leap SDK group. Quick Start now opens with a one-sentence technical summary and a backlink to the Overview. - Add deployment/on-device/sdk/overview.mdx with the positioning content: first-class LFM support, day-one model coverage, validated per-checkpoint sampler defaults, LFM-native chat templates, multimodal LFMs, constrained generation, one-call model fetching, plus the 'Other features' bullet list. Linked deep-dives at the bottom. - Strip the intro section from quick-start.mdx; keep the migration Info callout. New page is the sidebar entry point. - Insert overview at the top of the Leap SDK nav group in docs.json. - Re-point the legacy /leap/edge-sdk/overview redirect from quick-start to the new overview page (more meaningful landing for anyone holding the old URL).

Paulescu

Approving on behalf of @Paulescu via Claude Code. CI green; merging.

## Summary Adds `/deployment/on-device/sdk/overview` to `link-snapshot.yaml`'s `active:` list. ## Why PR #97 introduced `deployment/on-device/sdk/overview.mdx` but the link snapshot wasn't regenerated before merge, so `snapshot:check` is failing on main (run [26214732117](https://github.com/Liquid4All/docs/actions/runs/26214732117/job/77134086884)). The `leap/edge-sdk/overview` URL deleted by #97 stays resolvable via the existing `docs.json` redirect to the new page, so no `deleted:` entry is needed. ## Test plan - [x] `npx tsx scripts/generateLinkSnapshot.ts --check` passes locally (`Snapshot OK: 162 active URLs verified.`)

Copilot AI review requested due to automatic review settings May 15, 2026 17:41

iamstuffed requested review from a team and Paulescu as code owners May 15, 2026 17:41

Copilot started reviewing on behalf of iamstuffed May 15, 2026 17:41 View session

mintlify Bot deployed to staging May 15, 2026 17:42 View deployment

Copilot AI reviewed May 15, 2026

View reviewed changes

mintlify Bot deployed to staging May 15, 2026 17:49 View deployment

mintlify Bot deployed to staging May 15, 2026 18:11 View deployment

mintlify Bot deployed to staging May 15, 2026 18:23 View deployment

iamstuffed added 17 commits May 15, 2026 15:09

docs(android-sdk): align docs with 0.10.6 source

9c369c7

iamstuffed force-pushed the fix/android-sdk-qa-issues branch from 8b13e7f to 6650914 Compare May 15, 2026 22:11

mintlify Bot deployed to staging May 15, 2026 22:12 View deployment

iamstuffed added 8 commits May 15, 2026 15:54

mintlify Bot deployed to staging May 15, 2026 22:57 View deployment

mintlify Bot deployed to staging May 18, 2026 19:33 View deployment

mintlify Bot deployed to staging May 18, 2026 20:20 View deployment

mintlify Bot deployed to staging May 18, 2026 20:23 View deployment

mintlify Bot deployed to staging May 19, 2026 14:44 View deployment

iamstuffed changed the title ~~fix(sdk): apply v0.10.6 Android SDK doc QA fixes (DOC-27, DOC-37..DOC-60)~~ docs(leap-sdk): v0.10.6 QA fixes + critical audit + v0.10.7 refresh & artifact verification May 19, 2026

iamstuffed changed the title ~~docs(leap-sdk): v0.10.6 QA fixes + critical audit + v0.10.7 refresh & artifact verification~~ docs(leap-sdk): refresh through v0.10.7 + SDK doc QA pass (DOC-27, DOC-37..DOC-60) May 19, 2026

mintlify Bot deployed to staging May 19, 2026 16:53 View deployment

mintlify Bot deployed to staging May 20, 2026 12:53 View deployment

Paulescu approved these changes May 21, 2026

View reviewed changes

Paulescu merged commit 90ac327 into main May 21, 2026
6 checks passed

Paulescu deleted the fix/android-sdk-qa-issues branch May 21, 2026 08:28

Paulescu mentioned this pull request May 21, 2026

chore: refresh link-snapshot.yaml after #97 #99

Merged

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs(leap-sdk): refresh through v0.10.7 + SDK doc QA pass (DOC-27, DOC-37..DOC-60)#97

docs(leap-sdk): refresh through v0.10.7 + SDK doc QA pass (DOC-27, DOC-37..DOC-60)#97
Paulescu merged 32 commits into
mainfrom
fix/android-sdk-qa-issues

iamstuffed commented May 15, 2026 •

edited

Loading

Uh oh!

mintlify Bot commented May 15, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Paulescu left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

iamstuffed commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Section 1 — Original Linear QA (commits 3fa1aeb → 6650914)

Section 2 — Critical audit (commits 8a5f988 → 23cb977)

Section 3 — v0.10.7 docs refresh (commits 7c4394e, 7073608)

Section 4 — Artifact verification (commit 20e3a61)

Section 5 — Re-audit (commit bb19369)

Test plan

Uh oh!

mintlify Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Paulescu left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

iamstuffed commented May 15, 2026 •

edited

Loading

Section 1 — Original Linear QA (commits `3fa1aeb` → `6650914`)

Section 2 — Critical audit (commits `8a5f988` → `23cb977`)

Section 3 — v0.10.7 docs refresh (commits `7c4394e`, `7073608`)

Section 4 — Artifact verification (commit `20e3a61`)

Section 5 — Re-audit (commit `bb19369`)

mintlify Bot commented May 15, 2026 •

edited

Loading