Repository navigation
Assess post-v0.18 speech, LoRA and state fixes against the downstream bridge #75
Description
Current delivery snapshot — 2026-11-07
Owner v0.19.0 is published at f173fe9b18a30fdc23cc896be27a36bf85657921, upstream 83ce6067f2e2a3fb697556928f93936693ded971; all21 published assets match the independently qualified bytes. GitHub-enforced immutability is not claimed.
Core adoption/public C API1.0 activation is merged through core#1743, with ASR preservation #1748 and image-cancellation/utility preservation #1750. Public native CPU schema, embedding, Whisper ASR, matched Qwen image/history/recovery, utility calls and scoped Gemma4 audio evidence are accepted; corrected S24 evidence remains bounded to its exact20-case device/profile. Original failed collectors/semantic cases remain preserved. This is not general GPU, physical-iOS, LoRA or model-family parity.
Draft core#1746 retains qualified runtime19; its current source/software/artifact status belongs in the dedicated plan#1703. Core0.18 and all three Apple0.18 packages remain unpublished and require explicit approval after #1703's final independent acceptance (CUDA54/54 is recorded, not yet independently accepted). Published core0.17.5 still consumes the older runtime; owner publication, merged core adoption and package publication stay separate.
#97/#99/#100/#105 and core#1677 retain their focused acceptance/readback. The raw recurrent-state repair remains separate #70; no unbundled fix or broader retirement is credited here. Browser stable0.19/nightly0.20 and core's [email protected] pin remain independent; no Web terminal-cause closure.
Retained raw/browser/carry evidence.
New metadata-contract owner: metadata#107, actual callback2 versus manifest1; direct Dart probes are correct. Raw MTP/dependency/clone and qualification-watch delta remains separate from the published0.19 checkpoint.
New raw stable0.19.1/7a03724cece417f1724c923b3d527b4319730841 is separate from published owner19. The tagged three-commit diff adds default image capacity/existing-family backend configuration, with no identified C/header/carry-preimage change. Owner qualification plus reviewed consumer compatibility/prebuilt/topology/smoke mapping code and fixtures precede pin/checksum/SwiftPM sync; current tooling rejects0.19.1, so this is not a code-free bump; raw-main C API1.1/tool-choice/provider/state changes have different binding/probe/carry gates. Current mapping correction, raw6fc1a5b8 and watch reconciliation.
Original investigation and retained acceptance
The dated snapshots below are historical. This current snapshot supersedes their pin/publication facts, not their unresolved acceptance criteria.
Triage
P2 / enhancement / owner compatibility assessment. Separate from #19, which owns retirement of downstream workarounds, and #70, which owns Qwen3.5 conversation-state leakage.
Current layers / new evidence — 2026-10-21
- Published owner v0.18.0-2 remains owner
497e5ce0958dbd8927532af5acdeeaa0730495e6, upstreamb2f686e2ed4718fb84ec398a61dd59ca0f0aff27; published core 0.15.5, main and local checkout retain it. - New raw stable v0.18.1,
bda624851d74be34d4e1f7fac1fc4155939539c7, repairs a source-build EmbeddingGemma 2 ABI incompatibility through dependency/provider-prebuilt changes. The c/runtime/omni/js/models subtrees match v0.18.0; no new stable C/runtime source API is introduced. Changed binaries still require platform/loader/export/model qualification. It does not include owner Dedicated ASR: whisper-tiny .litertlm container fails to load (tf_lite_prefill_decode not found) #77/Expose why generation ended (token budget vs EOS) for consumers #78 repairs. - Raw main
13c208f1cf401bb024bd993f1debb00e90fc5bfbadds 11 commits since the previous scan: Qwen3.5 regex function-call metadata/parser (minimum runtime 0.19), GPU TopK sources, Kokoro voice/payload correction, NPU KV allocation/Jinja handling, additive C API 1.0 session clone and build-flag-gated LLGuidance tool constraints. Source availability is not qualified accelerator/strict-output/public Dart support. Pin→main history is diverged; do not interpret ahead counts as net-new capability counts. - Preserve raw C API 1.0 ownership gates: borrowed token access af319727 must not be independently freed or outlive its collection. Constrained MTP 80b2a969, adaptive speculation, CJK ASR deduplication, registry/proto/Omni removals and vision-buffer reuse retain their exact-candidate isolation/output/lifetime tests. The earlier tool-stop change remains reverted; it is not a #919 fix.
- Existing #79 (Whisper container, head
46d3400b90105c9fbbbc138a9a6c044380e57f25) and draft #80 (versioned native terminal cause, headea1acc5d9059c32cc8e529356ff332c79f537398) each have 19 passing checks, remain unmerged/unpublished and gate carries to audited v0.18.0. Current mergeability is clean, but integrating the second lane still needs new exact-head evidence. Reconcile Track and retire LiteRT-LM downstream speech/runtime workarounds #19's overlap patch and both new carries before selecting v0.18.1; no automatic tag/pin update. - npm is separate: registry latest currently says 0.18.0; explicit 0.18.1 exists. New nightly 0.19.0-nightly.20261020 now publishes binary blob transport and vision settings. Core #1153 owns media/browser qualification; neither version supplies a trustworthy browser terminal cause.
- Exact raw-main Linux 39551481954 and Android 39551481796 pass; push run 39551480679 fails with zero jobs. Keep this upstream automation anomaly distinct from owner release/platform failure.
Evidence and benefit
Published v0.18.0-2 still bundles upstream b2f686e2ed4718fb84ec398a61dd59ca0f0aff27. Raw main on 2026-10-15 was 61dcfc77225019e067580dceb3ea268483d1938c. Missing changes include ASR trailing-repetition truncation, resampling/TDT robustness, overlapping-chunk/timestamp repairs, LoRA buffer/state fixes, Kokoro language work and streamed tokenizer/loading changes. The owner v0.18.0-2 overlap source patch repairs a bounded window-merger defect, not these newer raw changes.
Primary evidence:
- google-ai-edge/LiteRT-LM@68c391c
- google-ai-edge/LiteRT-LM@61dcfc7
- google-ai-edge/LiteRT-LM@83ceffc
- google-ai-edge/LiteRT-LM@b2f2d9d
New compatibility evidence — 2026-10-16
Raw head is now 48b82892f1340013e6b0b42547c5b91ec712798d; owner/published upstream remains b2f686e2ed4718fb84ec398a61dd59ca0f0aff27. Upstream 39306c70 removes omni/asr/asr_engine.h and legacy ASR/TTS/Text2Image engines. Our pinned owner bridge includes that header and calls AsrEngine::Create / CreateSession: a raw source bump needs an Omni engine/registry adapter, not just a version change. c1312ccd also migrates C++ model-type callers to proto TfLiteModelType.
Quiet-speech thresholds, log-mel/short-tail handling, seam deduplication, first-chunk padding, Kokoro language G2P and TTS/image GPU caches are raw-only. They do not automatically close other speech issues. Core #673 is now fixed by our separate owner overlap patch and published core 0.14.0 adoption; do not treat that as migration to raw Omni APIs.
Additional raw compatibility deltas — 2026-10-17
Upstream removed the legacy ModelType enum (e30b1f58), renamed ASR/TTS paths to speech2text/text2speech (e5f94123), renamed config/metadata protos (776cdb6b) and their files/targets (f34fffcf). Audit includes, generated proto dependencies and registry/model inference, not just the earlier engine header. Qwen3-TTS language/prefill/GPU/metadata repairs (fb8440ec), Kokoro long-text/token-boundary fixes (e9980100), session-sampler MTP verification (b9b210d7) and tool-stop handling (c499bcf1) remain raw-only. Native TTS feasibility is separately tracked in llamadart#1161/#322; stop-limit propagation remains llamadart#919.
Published v0.18.0-2 / owner 497e5ce0958dbd8927532af5acdeeaa0730495e6 retains upstream b2f686e2ed4718fb84ec398a61dd59ca0f0aff27. Dedicated Whisper container loading is now #77, not a reason to claim the Moonshine overlap repair failed.
Acceptance
- Port and compile the owner ASR creation/session/model-type boundary against an exact candidate while preserving the public C ABI, config defaults, cancellation and reset semantics; retain pinned-v0.18 controls.
- Map each useful upstream fix to the actual downstream C++ ASR bridge/runtime call path; do not assume the Moonshine bridge uses every upstream decoder.
- Compare headers/exported symbols/struct and ABI-version contracts, prebuilt overrides, model format and existing source patches before choosing an exact release/candidate.
- Run representative push-PCM/backpressure, silence, overlap, finish/reset/cancel/reuse and affected LoRA/state tests; link llamadart #904/#673/#634 only when causally covered.
- Establish whether TTS or other capability additions need official C ABI/owner bridge/public Dart work. Preserve truthful capability probes and unsupported errors.
- Require owner-equivalent Linux/Android builds: missing mldrift_serialization_gen was repaired by 9e06e9de, while a separate zero-job workflow failure remains. Record both independently.
- Retain macOS arm64-only support and code-signing checks; do not infer missing x86_64 runtime support from a successful universal app launch.
- Coordinate checksums/manifests, consumer mapping/bindings as needed, docs and representative device qualification before adoption.
Boundaries
Tracking/qualification only. This issue does not authorize publication, workflow dispatch, paid hardware runs, downstream pin changes, or weakening supported-channel policy. No PR-caused regression is alleged without a causal reproduction. Preserve immutable historical artifacts and record unavailable models/hardware explicitly; CPU/software fallback is not hardware GPU qualification.
Activity
leehack commentedon Oct 17, 2026
Material boundary update: owner v0.18.0-2 is published and adopted by core #1148 / 0.14.0; upstream stays b2f686e2 and #673's overlap repair is a carried patch. Raw main advanced to 48b82892, with additional engine/proto renames, Qwen3-TTS/Kokoro and sampler/tool-stop changes. Updated adapter acceptance; these gains still require owner porting/builds and affected-family validation. Latest raw CMake workflow 39001104292 again failed with zero jobs, while populated Android/Linux/macOS/Windows lanes succeeded: do not generalize this as a failed owner release.
leehack commentedon Oct 18, 2026
Raw-only speech delta: 79c78433 discards Parakeet TDT token bursts after forced SOS; raw main is now 9a5f0ae1, also adding default Omni TTS/image remote URLs and model-card tooling. These are not new model families or additions to unchanged published v0.18.0-2 / upstream b2f686e2. Core #1172 now implements native CPU multimodal embeddings against that existing artifact; it does not solve the raw Omni/ASR port or qualify native GPU/Web embeddings. Current raw CMake workflow 39096360202 still fails with zero jobs while populated platform lanes pass. Preserve the bridge/API/build and affected speech tests before any raw adoption.
leehack commentedon Oct 19, 2026
2026-10-19 raw-only delta: 73abd38c repairs CJK ASR window duplication; 26dbb03a adds resource/backend registries. Added exact port and CJK/mixed-text/punctuation/ASCII controls, not a claim that the carried owner overlap patch covers these new paths. Public core 0.15.1 still consumes unchanged v0.18.0-2. Recorded the current zero-job CMake failure separately from passing populated Linux/Android lanes. No new model-family, artifact or pin adoption.
leehack commentedon Oct 20, 2026
2026-10-20 raw-candidate gates: borrowed token ownership, constrained-MTP state/mask fixes, Web vision transport and explicit enum/version/header checks. The earlier tool-stop change was reverted, so it is not a current raw gain or #919 fix. Refreshed the current block and manifest URL; unchanged owner v0.18.0-2 is consumed by core 0.15.4. The current raw zero-job CMake failure remains distinct from passing populated lanes. No automatic ABI/pin upgrade.
leehack commentedon Oct 21, 2026
2026-10-21: added newly published native v0.18.1's EmbeddingGemma 2 dependency/prebuilt ABI repair, separately from raw-main C API 1.0/Omni migration. Owner v0.18.0-2 and core 0.15.5 pins are unchanged. Existing #79/#80 carries and #19 overlap-patch decisions must be reconciled before upgrading; identical stable headers alone do not qualify changed provider binaries. Refreshed raw/new npm candidate and zero-job-versus-populated-CI evidence without changing priority or acceptance.
leehack commentedon Oct 22, 2026
2026-10-22 delivery and candidate update — retain P2 owner compatibility scope.
Published v0.18.0-3, owner
8182448814867ad329be7e995b4e8aab5efd79c8, retains upstreamb2f686e2ed4718fb84ec398a61dd59ca0f0aff27; manifest SHA-256e7feaeec7db05f7202181f02ec2afd3ae7ea8169e5e15bf931ff7841bbef3061. It publishes #79 ASR-container routing and #80 conversation finish reasons, now pinned by core 0.15.6 / LiteRT companion 0.15.2. Core#919 still lacks two proxy bindings; Session streams/Web remain outside that repair.The selected stable upgrade is still v0.18.1,
bda624851d74be34d4e1f7fac1fc4155939539c7: dependency/provider-prebuilt EmbeddingGemma 2 ABI repair, no c/runtime/omni/JS source API change. Existing draft #81, headdf2053340b0c3462e45d67eb617539e4de162b34, has 19 passing exact-head jobs, including builds and desktop Qwen smoke. Its qualification/evidence handoff remains incomplete; these unrelated-model smokes do not alone qualify EmbeddingGemma 2 or Apple GPU behavior. No v0.18.1 owner artifact is published.#81 retains ASR/terminal/overlap/loader/Dawn protections and adds a v0.18.1-only Bazel WORKSPACE/.bazelrc compatibility carry, with postimages matching upstream d99b438f. Coordinate the existing lane; no newly justified patch retirement. #19 owns removal conditions. Raw C API1.0/Omni is a separate migration.
Raw main a85bb454b473653502e29c6c2ed4488bf0b19981 adds Web audioBackend/streamed encoders, prefill context exhaustion, adaptive speculation, MiniCPM5 regex/XML metadata (minimum0.19), empty-history template guards, Parakeet GPU-encoder/CPU-TDT routing and FP16 GPU defaults. These are raw-only existing-family/correctness/config changes, not new public Dart families or measured speedups. Preserve actual template, sampler/constraint/state-isolation, context, ASR/audio and precision/output controls.
Upstream #3945 closed unmerged/moved internally, not a #70/#672 zero-state repair. Populated raw platform lanes pass, but 39723942044/39723933131 fail with zero jobs; this is not owner release failure. Native publish verification recovered before successful publication, so no current stalled release is established. Browser npm remains separate and unchanged; no new audioBackend/terminal-cause package delivery.
leehack commentedon Oct 22, 2026
Status: owner candidate for upstream v0.18.1 is up as draft #81 (head
df20533). All 19 CI checks pass (run 39705720587); the ASR overlap, container-routing and finish-reason carries are retained, and a local macOS arm64 build passes the Whisper, Moonshine, container-control and finish-reason ABI smokes. Not yet run: EmbeddingGemma 2 inference, Qwen3.5 state reuse, Android/iOS device checks, independent review. Nothing is released or pinned; #75 stays open.leehack commentedon Oct 23, 2026
2026-10-23 delivery delta — retain P2; distinguish stable adoption from raw migration.
Published v0.18.1, owner
7adc3749f9a8da2259f878e26bd09b5baf5c1f70, bundles stablebda624851d74be34d4e1f7fac1fc4155939539c7. #81 and release run are complete; core#1320 adopts it on main. Public core 0.15.6/LiteRT companion 0.15.2 still consume v0.18.0-3; existing core#1334 owns pending 0.16 publication, so no duplicate adoption lane.#81 now includes packaged baseline/candidate-without/candidate-with-carry evidence: overlap, ASR-container and finish-reason repairs remain required. A v0.18.1-only WORKSPACE build carry is also recorded; no active behavior repair was retired. EmbeddingGemma 2 CPU passes, but macOS GPU remains guarded because the accelerator prebuilt is unchanged and crashes; do not infer GPU repair from dependency/source compatibility.
Raw main 25016d6 adds 16 commits since yesterday: multi-context NPU MTP, engine/session speculation defaults, single-object/parallel-tool message contract, GPU linkage and benchmark-template correction. Async KV refill was reverted; no measured consumer speedup or new family is established. C API1.0/Omni/ASR ownership migration and #70 state acceptance remain separate.
Browser npm nightly20261022 now actually publishes audioBackend/multimodal setup (core#1153), but lacks reliable terminal cause. Native finish reasons already exist since v0.18.0-3 and remain unbound in current Dart main (core#919); a newer owner release is not that missing step.
Raw Android Bazel 39909988202 fails on Maven dependency timeout, not established source regression; CMake/Linux/macOS/Windows pass. Raw push 39909989599 and 39909981914 fail with zero jobs. Keep these distinct from healthy owner publication. No raw pin or workflow mutation performed.
leehack commentedon Oct 24, 2026
2026-10-24 corrective artifact and raw-boundary update — retain P2.
Published v0.18.1-2, owner/tag
06f85a5940a6f2cd37529b85d53dd7ccd4c5e430, retains stable upstreambda624851d74be34d4e1f7fac1fc4155939539c7. Manifest SHA256d8ee78d3c35446507489a1d2eddac57232b90f2dd216940a4ff7a2df179afc15verifies. Preparation40012363772 and publication40020807463 succeed; skipped rebuilds are verified candidate promotion, not missing build evidence. Core#1352 adopted it; during this scan core#1365 merged and core0.16.1 published. Actual archive SHA256 5e26399bb1437f893414467fe1d95b52b0a34a663c3a1f91cf6fa49acfcaabdc and v0.18.1-2 pin verify. Core publication is complete; LiteRT companion0.16.1 also published at09:19:42Z with core constraint >=0.16.1 <0.17.0 and actual SwiftPM pin v0.18.1-2. Its archive SHA256 27e2240b232ebf9c61990c465ffd971f7c1569fb1bd92941bcd3799b4ed07e6c verifies. Remaining post-merge checks are separate from package availability.Mechanisms: #83 restores prior PF32 SME2 kernels for deterministic output; #85 disables int4 PQS8/QC4W SME2, restoring Gemma4 default-thread decode. #86 documents the trade-off: M4 Max one/two-thread prefill falls about42–44%; explicit1–2thread SME2 phone sweeps remain unmeasured. Released core0.16.1/#1365 now qualifies iPhone16Pro at default threads (decode1.2×, prefill about29% slower, unchanged output), as well as M4. The 1x64 DOT kernel is non-production. Do not advertise a universal performance gain or retire these carries from a green build.
Raw ee50b5bb advances23 commits since yesterday. Adoption must audit size_t counts/indices, by-value constraint enum, Linux/Android C-only symbol map/version node, and removed prebuilt TopK samplers. Preserve ASR/Omni migration and wrapper-export/loader closure, regenerate exact bindings and qualify model/state/cancel/constraint behavior. Moonshine follow-up reconstruction and modality inference are raw-only, not #70/#919 fixes.
Core#1367 records Linuxarm64 embedding creation failure and Windowsx64 process crash on baseline as well as candidate. Cause is not assigned to SME2 or this rebuild; chat passes. Consumer fail-closed work is now P2; root-cause owner work remains to be isolated. Existing #82/#84 closures do not establish all-platform embedding support.
Raw populated platform lanes pass, while 40065972779/40065966816 fail with zero jobs. No current owner publication failure. Browser nightly contracts remain separate; no new family, raw pin or hardware claim.
leehack commentedon Oct 25, 2026
2026-10-25 delivery/raw delta — retain P2; latest published artifact is already consumed.
v0.18.1-4, owner6162d448be3ec91c5f7766863c894c1e5f108ad5, retains upstreambda624851d74be34d4e1f7fac1fc4155939539c7. Fresh manifest SHA2567f5cb32a4da7e37d42976c665366057badb86b2baa1f06d44f86e1d1660a3605 verifies; publication40128843262 succeeds. Public core0.16.2/LiteRT companion0.16.2 now pin it (actual archives/hash/SwiftPM verified); no further automatic pin bump or duplicate adoption lane.
Raw 9a9a74fc1e22831a7888e3ed7e40f73b510016b8 advances four commits. Parakeet45e6d8be changes warm-start, overlap0.4→0.75, silence/timestamps, copies/locks and CPU defaults. Qualify short/silent/repeated chunks, confirmation boundaries, reset/cancel/reuse and output/latency rather than importing a speedup. Artisan Web maxNumImages/streamed-reader changes are existing-family configuration, not new family support.
Before raw adoption retain C API1.0 size_t/enum/export-map/TopK packaging audits and port the owner ASR bridge off the removed omni/asr/asr_engine.h. Existing overlap/container/finish/loader/Dawn/SME2 repairs and new CPU-options carry need explicit retirement controls, not a non-applying patch.
Raw populated platform lanes pass; 40140463563 fails with zero jobs, separate from healthy owner publication. Upstream#4178 cache-deserialization report is not a demonstrated owner exposure or #70 state fix; #4175 lacks exact runtime/repro. #70/#71/#3165/XNNPACK watches otherwise unchanged. No new device/model execution or pin/workflow mutation.
leehack commentedon Oct 26, 2026
2026-10-26 dependency/binary candidate delta — retain P2; no new owner upgrade.
Published owner remains v0.18.1-4, owner6162d448be3ec91c5f7766863c894c1e5f108ad5, upstreamstablebda624851d74be34d4e1f7fac1fc4155939539c7. Public core/LiteRT companion0.16.2 and frozen0.16.3 prep retain it; no further artifact adoption is needed for that release.
Raw 292d4e52c8daac8e5c3fd910ec65d284facf17f2 changes WORKSPACE and27 prebuilt pointers, not LM C/API/model source. LiteRT becomes dcb657e8, TensorFlow4f8e6d47. The dependency delta includes proxy ABI/version checks, registry/interposition and host-mapped-buffer changes. Changed Apple Metal/Dawn/Linux/Windows binaries require new symbol/provider/loader/signature and affected-model/device evidence even when LM source is unchanged.
No paired new-prebuilt option propagation or #1367 embedding creation was executed; do not retire the CPU-options identifier carry, GPU guard or signing protection from source/postimage inspection. Existing C API1.0/Omni/ASR migration and #19 original-trigger gates remain.
npmnightly20261025 has unchanged conversation/settings JS fingerprints versus24, but four changed WASM fingerprints despite identical sizes. Pin a matched package payload set; source-JS equality is not binary equivalence or a new API. Single-message/audioBackend/maxNumImages semantics and missing Web terminal cause remain unchanged.
Upstream#4183 reports severe CPU-audio fallback latency for an NPU Gemma4E2B bundle variant on SM8650; third-party runtime/model evidence, not a new family or established llamadart exposure. #70/#71/#3165/XNNPACK watches unchanged. Populated raw platform lanes pass; 40272112466/40272108031 fail with zero jobs, separate from healthy owner publication. No new test/hardware/pin/workflow action.
leehack commentedon Oct 27, 2026
2026-10-26 llamadart 0.17 runtime-upgrade assessment: no upgrade target yet. Stay on owner v0.18.1-4 (upstream
bda624851d74be34d4e1f7fac1fc4155939539c7) and retarget when upstream tags v0.19.0.Why not now
da28df6ais 326 commits ahead (v0.18 branched 2026-09-24) and already declaresVERSION = "0.19.0"andC_API_VERSION = "1.0.0", so a stable v0.19.0 will carry the same ABI break. Porting a moving raw head now means porting twice.size_tcounts/indices). About 98 of the ~169litert_lm_*symbols core references change signature, andlitert_lm_get_last_error_code(bound inlitert_lm_last_error.dart) is removed. Core needs regenerated bindings and a rewrite of every LiteRT call site, gated by the newlitert_lm_get_api_version.omni/asr/asr_engine.his gone. The owner ASR bridge (ABI v1) builds onAsrEngine::Create/CreateSessionand anAsrEngineConfigbuilt from a model path. Raw main replaces that withomni/speech2textandOmniEngine::Create(model_name, …), a name-keyed registry with remote-URL defaults. The bridge needs a real port, not a header rename, and every ASR real-model smoke has to rerun.prebuilt/*/libLiteRtTopK*Sampler*absent on main). Apple packaging currently shipsLiteRtTopKMetalSamplercompanions, so packaging and validation change.What raw main adds (all unqualified)
litert_lm_get_api_versionlitert_lm_session_clone(conversation clone already existed)conversation_wait_until_done, benchmark max tokensNone/LlGuidanceenum and by-value constraint typerun_text_scoringsemantics (now withsize_t/status changes); no logits/top-K: #1158 unchangedgated_delta_update)Carried patches on a future v0.19 candidate
4f8e6d47→ XNNPACK28d1fc6d(2026-10-19), which still descends from both defective commits (70a9c5e8,76fa737a).src/configs/gemm-config.cchanged sinced89ef666, so both patches need rebasing to new preimage hashes. XNNPACK 51645a04 (2026-10-26) adds SME2 QP8/QC4W ACLE kernels; that is a different path and not in any LiteRT pin.dcb657e8still returns"cpu_options". Keep it until the refreshed Linux/Windows prebuiltlibLiteRtis shown to read that identifier.c/conversation.cc.omni/speech2text; the removal controls stay with Track and retire LiteRT-LM downstream speech/runtime workarounds #19.d99b438f).dcb657e8/ the new deps..ldsC-only export map is attached to upstream's own shared target. The owner//bridge:libLiteRtLm.*targets link//c:engine, sostream_proxy_*export survives, but CI's symbol checks must confirm it.Trigger and plan when v0.19.0 is tagged
QUALIFICATION_*to the exact tag. Rebase/retire the carries above with baseline, candidate-without and candidate-with controls.speech2text, keeping the C ASR ABI v1 (or version it). Update TopK/Apple packaging and the symbol inventories.No pin, workflow, tag or release changed.
leehack commentedon Oct 27, 2026
2026-10-27 delta after the recorded da28df6a assessment — retain P2 and the tagged-v0.19.0 hold.
Published owner remains v0.18.1-4, owner6162d448be3ec91c5f7766863c894c1e5f108ad5/upstreamstablebda624851d74be34d4e1f7fac1fc4155939539c7, already consumed by public core0.16.4/LiteRT companion0.16.2. No new stable/owner release or carry retirement.
Rawdab2e708dc5750549685692863039c5a954c3a35 adds seven commits after the assessment:
New state watch #4195/open #4197: rewind leaves last_prefill_token_id stale. Keep rewind→score/continuation/reference controls separate from #70's recurrent-buffer leakage. Reporter cross-backend scope is not owner reproduction or a merged fix.
npm remains latest0.18.0/nightly20261025; explicit26 is absent. Raw streamed-reader/Blob changes are not newly published package behavior. 40459885157/40459876340 fail with zero jobs, while populated platform lanes pass; removing push triggers did not establish repair.
Preserve the existing C API1.0, ASR bridge, TopK packaging, optional exports/version probes, bindings/call-site, signature/loader and real-model/device gates. Core#174's new bounded native schema implementation uses the existing owner, not raw0.19 ABI; it is source-only for0.16.5. #919 Web terminal cause remains missing.
3 remaining items
leehack commentedon Oct 31, 2026
2026-10-31: tagged v0.19 candidate now exists; owner publication and consumer migration remain pending. Retain P2.
Upstream v0.19.0 is771b06e1a2c7f70a399a718599109facf37e38fd. Draft #92, headcccc17645668fe0eb7c330460c1e9944683ffcf8, has 19 passing exact-head checks, including eight target builds and three desktop Qwen inference lanes. Published owner remains v0.18.1-4, selected by public0.17.0/main; this is not a delivered upgrade.
The tag-specific audit supersedes raw-main assumptions: tagged0.19 retains prebuilt LiteRt/accelerators/Dawn and excludes the later Windows FD repair. Several carries retire, while overlap/finish-reason ports, SME2 rollbacks and Android Dawn qualification remain. C API1.0/ASR changes require the planned minor-release migration, not a patch or pin-only update; cancelled sessions/conversations must be deleted, not reused.
Android/iOS devices, rollback-Dawn compatibility, real Parakeet and GPU/NPU ASR remain unverified. #93/#94 already own the Linux runner/glibc repair. #70/#71 and core#672/#1367 remain unresolved; the published typed embedding guard is not a runtime repair.
Raw main76e08ce8c8172d9717cda71d624c7d46b3c2113f adds19 commits, including audio snapshot/restore, static draft verification, selected C/Python signatures, dependencies and MiniCPM-o stages. Keep them distinct from the tagged candidate, browser package and qualified Dart support. No new duplicate ticket, workflow, artifact or consumer change was made.
leehack commentedon Nov 1, 2026
2026-11-01 raw-source delta — retain P2 and the existing tagged0.19/minor-migration gates.
Rawmain76e08ce8→67ac10b550e1af358f8d04687be6ce5e87a3a433 adds seven commits:
Stabletag771b06e1/#92candidatecccc176 remain unchanged; ownerv0.18.1-4 is still the latest published artifact and selected by publiccore0.17.2/main. Linux-floor#94 merged without a new artifact. No automatic pin/API change is justified.
New browser nightly0.19.0-nightly.20261031 (registry) has no relevant inspected contract change versus stable0.19.0: engine/settings/content/Wasm declarations are identical, and streaming still lacks terminal cause. Keep #919 loops refused and #1153 media qualification separate; no repeated unchanged comments are needed there. No new family, owner publication or model/device run is claimed.
leehack commentedon Nov 2, 2026
2026-11-02 raw/lifecycle watch — retain P2 and the existing owner-before-consumer gates.
Raw main 964d72e8d2fc6225b035219648533fc997e32d46 adds mutex-protected streamed-weight registration and thread-local model-compilation context. b91a4d7b adds a 16 MB Qualcomm embedding HTP read budget. Existing free-function signatures are unchanged; neither establishes owner/Dart concurrency, NPU, memory or speed qualification.
Open upstream #4330, #4331 and #4333 propose tool-choice exposure/behavior and independent encoder lifetimes. They are not delivered APIs. #3771's new iOS report warrants timeout/error, callback-drain and destruction controls during core #1677 migration. Its production artifact is 0.17.0; claimed later-version exposure is reporter/source-derived, not independently reproduced here or confirmed in llamadart.
Published owner remains v0.18.1-4 on bda62485; public core 0.17.5 retains it. Draft #92 is unchanged. #95's signing repair is source-merged and covered by #71's fresh update; repaired runtime publication/adoption remains separate. No duplicate signing comment or migration ticket is needed.
New npm nightly 0.19.0-nightly.20261101 has six inspected JS/declaration files identical to stable 0.19.0; no terminal-cause/media contract advancement was found. Keep #919 loops refused and #1153 qualification separate. No new family, artifact, pin or model/device execution is claimed.
leehack commentedon Nov 3, 2026
2026-11-03 delivery/qualification update — retain P2; no native pin-only upgrade.
Owner #92 is merged, not a draft. Source5129cd00003506f3b22a1d7400022fba97e9476c includes callback-copy loss #98; full preparation41563859000 passed. It selects upstream v0.19.0 at83ce6067f2e2a3fb697556928f93936693ded971. Published owner remains v0.18.1-4/bda62485, selected by public core0.17.5 and main. Internal CPU/streaming/settlement preparation is source-delivered, but public C API1.0 dispatch remains disabled; core#1677/#1734 own migration and artifact admission.
Required blockers are explicit: #100's unchanged Unicode-schema test must pass a new packaged candidate after draft #102's source repair; #99 retains truthful text-LoRA refusal, not setter-only support. #101 is semantic qualification, with the independent source checkpoint reproducing preserved wrong output bytes; it is not a demonstrated candidate-only runtime regression or an accuracy pass. Preserve original prompts/oracles/failures and reference-review disposition. Signing #71 and allocation-loss #97 also retain publication/adoption gates.
Raw main131d164e adds Web MTP controls/stats, independent encoder lifetime/cancellation, speculative lenience, NPU vision masks and Qwen3-TTS stopping. They are not automatically in the tagged candidate or native owner.
New npm0.20.0-nightly.20261102 actually publishes speculativeDecodingConfig; core#1156 now owns candidate integration/qualification. Engine drafter loading, one-candidate constraints and lenience/output semantics need controls; nonzero lenience is not exact sampling. Stable/browser pins are unchanged, and terminal cause is still missing (#919). No model/device run, owner publication or consumer pin change was performed.
leehack commentedon Nov 4, 2026
2026-11-04 layer/qualification update — retain P2; no published0.19 owner artifact or automatic repin.
Published v0.18.1-4 / upstream bda624851d74be34d4e1f7fac1fc4155939539c7 remains the main/public core0.17.5 pin. Owner main f173fe9 targets v0.19.0 /83ce6067f2e2a3fb697556928f93936693ded971. #104's unchanged Mac CPU Unicode/schema diagnostic now passes; #105/#106 record merged Android protobuf isolation and accepted bounded public CPU creation/results. Final S24/affected-path checks, qualified publication, core/SwiftPM adoption and final consumers remain in core#1677/draft#1739. Prepare41809780904 has active platform jobs, not a zero-job/stalled release.
Raw main d053a1aecc41738b6247d77f756be085a22550d2 is separate. Step-zero recurrent-state reset e1f86b05 explicitly addresses upstream#3165, but is absent stable19/candidate/published18.1-4; #70 owns original repeated-conversation CPU/GPU qualification. Other raw changes include per-call encoder cancellation and empty tool-response handling. No new model family today; no unrelated carry retirement.
Current v0.19 qualification inventory records retired ASR-container/WORKSPACE/CPU-option/SentencePiece-NUL/old-MetalTopK workarounds; retained ASR-overlap/finish-reason/SME2/iOS-accelerator/Android-Dawn carries and new HF grammar fixes. Android protobuf isolation is link policy. Preserve exact provenance and gates; do not delete carries just because raw reset landed.
Browser remains independent: stable npm0.19.0, core example [email protected]. Published0.20.0-nightly.20261103, SHA1 8930440709857c5e1badbb1fff98cd86da067304, now ships WasmResult/unwrapWasmResult matching 32a61296's JS error-boundary repair. No gitHead is published; package contracts do not prove native reset containment. Normal stop versus output/context exhaustion still lacks a reliable Web cause; core#919 tool-loop refusal remains. Existing media/MTP umbrellas suffice.
#101 closed as reference-model behavior, not a runtime numerical fix; #99 LoRA refusal and #71 final signing-artifact adoption remain. Raw current platform CI passes; the older stable-tag legacy CMake run41490136893 still fails with zero jobs, an unchanged upstream automation watch. No model/device/workflow execution or pin change in this scan.
leehack commentedon Nov 5, 2026
2026-11-05 new raw/metadata watch — the current published/adopted0.19 checkpoint is already in the body; no duplicate publication update.
Confirmed owner metadata defect now has #107: v0.19 manifest declares callback ABI1, while its exact published Mac library statically returns2; generator and validator repeat the wrong1. Main correctly probes callback2/allocation1, so no present Dart execution failure or automatic core release blocker is established. Preserve existing bytes; version-aware metadata plus packaged-getter agreement needs bounded owner repair.
Raw9936aa32d8362ff438af333d5d7704e857ed1344 remains separate: e032ec3e repairs MTP constraint-state/output-event lifetime; de80bb14 permits draft verification after media-end tokens; ca636dbf preserves GPU decode for mixed embedding/token inputs. All are absent stable0.19/owner/current Dart pins. e31a1234 refreshes LiteRT/TF/Dawn dependencies: re-audit carries/prebuilts/ABI/device behavior before any future raw candidate.
New GPU clone#4394 has maintainer Mac reproduction; inspected Dart paths do not call clone, so track future state admission rather than a shipped Dart regression. Qwen2.5 KV-capacity#4384 is an official-bundle reporter case; metadata-free dims[2] fallback exists in83ce, but no owner model reproduction or general-family failure is claimed.
Upstream maintainer confirms thinking/schema8b7bb5c2 (#3463) and scoring-rewind b8b3131f (#3561) fixes first in v0.19; issues remaining open does not negate that source evidence, nor establish new public Dart scoring support. JNI Unicode#1616 closed stale, not fixed. Bridge82/browser stable19/nightly20261103 and Web terminal-cause limits are unchanged. No new model family or model/device/workflow execution.
leehack commentedon Nov 6, 2026
2026-11-06: new raw stable0.19.1, plus separate raw-main API/qualification changes. Retain P2; no automatic repin or new0.18 scope.
LiteRT-LM v0.19.1,7a03724cece417f1724c923b3d527b4319730841, is only3 commits after83ce6067. The tagged diff leaves C headers/entrypoints, WORKSPACE/prebuilts and carry preimages unchanged. It defaults image capacity to4 while preserving positive overrides; release notes advertise Gemma4 media/Artisan backend combinations, not a new family. No new wrapper/binding ABI is demonstrated for this tagged update. A qualified owner artifact and platform/model/loader/carry checks still precede mechanical pin/checksum/SwiftPM synchronization; exposing new Artisan configuration would be separate work.
Latest published owner/current main remain v0.19.0/f173fe9b/upstream83ce6067; public core0.17.5 still uses18.1-4. Raw-main5667f3dfe0ec33afe24fde217fb6c393bf9b1db5 is a different candidate: C API1.1 tool_choice dc5166e7 needs owner exports, generated bindings, version/capability probes and real tool constraints before mapping existing Dart choices. SentencePiece LLG4ef337b7 overlaps our provider carry but does not establish ByteLevel/default-whitespace equivalence; adaptive MTP state c6669ff6 changes session/RNG ownership. Renew original byte/seed/state/constraint controls, not blind patch deletion.
Watch reconciliation: upstream#3463 now has matched reporter closure for thinking/schema fix8b7bb5c2, first0.19; upstream#3772 cache reuse/f540136c is reporter-verified fixed first0.19; upstream#3846 NPU repairdb0bd00c first0.19 has reporter19.1 verification, not owner NPU admission. upstream#4045 is source-fixed by3e24a714/upstream#4446, absent19/19.1; this advances a future Web-embedding candidate, not core#1157 wiring or core#1367's desktop cause.
upstream#4080 closed via LiteRT#11608/156ea9ae, but published wasm-utils2.6.0 still has unconditional importScripts. New core nightly0.20.0-nightly.20261105 has no gitHead; dependency/fix containment is unverified. Do not silently weaken CSP for its eval fallback. Newupstream#4423 Exynos/Xclipse ASR vendor-crash report is unconfirmed owner exposure; CPU/Adreno controls do not qualify that GPU.
#107/#108 already record current metadata source/CI progress; no duplicate update. Corrected published artifacts/adoption remain pending. Bridge82, Web [email protected] and terminal-cause refusal remain unchanged. No new family or model/device/workflow execution.
leehack commentedon Nov 7, 2026
2026-11-07: correct yesterday's “mechanical sync” implication. Detector42232767423 reports official0.19.1 artifacts READY but is preparation-only; it neither builds nor publishes. Current consumer sync mapping explicitly rejects >0.19.0, and the smoke allowlist/tests reject0.19.1. Adoption therefore needs reviewed compatibility/prebuilt/topology/smoke mapping code and fixtures, then qualified owner artifacts, pins/checksums/SwiftPM. The tagged three-commit diff demonstrates no new C ABI, but this is NOT a code-free pin bump.
Owner/main/local remain v0.19.0/f173fe9b/upstream83ce6067; public0.17.5 remains18.1-4. Raw stable remains 0.19.1/7a03724c; inspected main6fc1a5b8cc79cc349c33b7b99b27497777e0fedb adds no new family/C-header delta today.
Raw-only session state e40257f9 fixes source lifetime/KV-copy cases#4406/#4407, without a containing stable or proof that#70/#3165/#4394 are fixed. Renew switch/step0/released/rollback/clone controls. HF-tokenizer mutex317fb5d1 also requires concurrent/carry controls. Externalized weights df8bb66c are internal TFLiteWeights sections in the SAME .litertlm file, not filesystem sidecars/new resolver API. Minimum runtime19 needs conversion/version guidance and representative owner/Dart file validation; older-runtime checks warn only.
Watch reconciliation: #3986 reporter tests its file working with PyPI19 versus18.1, with no known fixing commit/owner reproduction. Kokoro#4046 retests19.1 only with force_fp32_on_gpu=true, not defaultFP16; c09b887f9 already belongs to the LiteRT dependency used by BOTH19/19.1. #3577 closes on changed-metadata19.1 retest, not original-bundle/AAR proof; #4125 has maintainer fix assertion without exact revision/reporter verification. #3443 replaces a withdrawn bad bundle, not a runtime fix.
#107/#108 already record the merged metadata repair; corrected artifact is unpublished and core#1772 is held post0.18. No carry retirement, new family, model/device/job or publication change by this scan.
leehack commentedon Nov 8, 2026
2026-11-08: v0.19.1 is now published, owner1fa4d43705fe07ba5e4d962e41cf32b8a2ac6116/upstream7a03724cece417f1724c923b3d527b4319730841,21 assets/manifestSHA2566ee1528a37f7e473c23def3dacfcdad1d9631cf7ed54d9891264e346e1d17e2e. It includes corrected callbackABI2 metadata. Core#1785,merged60b616f1, implements the reviewed19.1 compatibility/prebuilt/topology/smoke mappings, fixtures, pin/checksum/SwiftPM changes and independent acceptance. Yesterday's “tooling rejects19.1/unpublished” blocker is superseded; no additional base19.1 pin implementation is needed. Main/local now use19.1; publiccore0.18.0 uses19.0/83ce6067. Next coordinated core/Apple release is0.19.0, not a0.18.x patch (plan#1786).
New P1 core#1795 records actual Linux x64 Vulkan/Windows x64 D3D12 first-decode crashes in published19.1. Owner#112,mergedcaaa8a738c1dbad4eb5d6c7db77246b8123b08c2, repairs the mixed-C++-runtime boundary by source-linking LiteRT/accelerator into the host; PR4243061493219/19 and postmerge42439497569 pass. The proposed19.1-1 repair is NOT published. Exact artifact provenance, audit follow-ups#113, acceptance/approval, consumer checksums/SwiftPM and actual desktop GPU/lifecycle gates remain. Whether public0.18/runtime19.0 has the same GPU defect is unresolved: do not call it a proven shipped regression.
Closed owner#111 is source repair, not consumable embedding delivery. Core#1367 guards stay until repaired published artifacts and exact consumer model/reference/lifecycle evidence justify each platform; Androidx64 remains unqualified.
Main Web now adopts npm0.19 via#1788; Gemma4-web WebGPU and Qwen3 CPU history subsets are recorded, while terminal cause/templates/embeddings refusals and Qwen3 GPU multi-turn limits remain. Public0.18 Web stays18. Raw-main02d7e8d80cb75cbb03d8cba4c63f51e2eb318ec5 adds only NVIDIA NPU/MTP next-draw feed today, no new family/API. Nightly advances20261107, not stable capability. Current raw Mac CI42469582778 fails cache-clean build-output cleanup, not demonstrated runtime regression. Detector#109 is intentionally manual-only, not a missed automatic update. No carries retired or jobs dispatched by this scan.
leehack commentedon Nov 8, 2026
Status 2026-11-08: v0.19.1-1 is published (prerelease, desktop in-process LiteRT from #112). llamadart adoption is in llamadart#1808.
leehack commentedon Nov 9, 2026
2026-11-09 delivery correction: core 0.19.0 now publicly consumes native v0.19.1-1, owner 82d4ae1 / upstream 7a03724cece417f1724c923b3d527b4319730841. Core #1808 records qualified desktop CPU embeddings and L4 Vulkan/D3D12 recovery; #1367/#1795 are closed. It also executed public0.18/runtime19.0 GPU controls: 3/3 crashes on both hosts. Yesterday's older-release exposure uncertainty is resolved, not merely inferred from shared source.
Newest published rebuild is v0.19.1-2, owner 0b15fb3, same upstream; manifest SHA256 0c4ec985c8a655cfb1e7d1ca5ede22474b9bd7caf1a0369cf44c0812e414041d. It adds #115's in-process weight-handoff marker and #117's tests/docs, with unchanged C API1.0.0/callback2, six carries and Android overrides. No model addition or patch retirement. Rebuilds are prereleases; /releases/latest still returning unsuffixed19.1 does not mean -2 is unpublished.
Public0.19 and local ec4bf4f8 still pin -1; concurrent batch#1843 merge1fdc222f at10:03UTC moves GitHub main to -2. Draft #1830, 0296fd58, already implements -2 checksums/SwiftPM and exact marker1 desktop embedding admission, with GCE/S24 qualification. It was integrated in audited/green batch#1843, 810d9a29, now merged on GitHub main but not public. #1824 owns the remaining integration/final-release acceptance; do not schedule duplicate marker/pin implementation. Marker1 is not GPU qualification or protection from external global-library interposition. Software-GPU#572's #1831 guard is also source-delivered through that batch, not yet public.
Bridge83 and Web LiteRT19 are now public in core0.19. Qwen3-TTS suppress-token repair is delivered within its recorded subset; Chatterbox Web, wasm32 TTS, terminal-cause loops, media/templates and Web embedding parity remain separate limits.
Raw stable19.1/main02d7e8d80cb75cbb03d8cba4c63f51e2eb318ec5 are unchanged since yesterday; npm nightly advances to 0.20.0-nightly.20261108, not a new stable capability. Owner/bridge release flows are intentionally manual; -2 publication succeeded. No new owner automation failure or carry retirement, source/pin/workflow/model/device change by this scan.
leehack commentedon Nov 10, 2026
2026-11-10: public core0.19.3/main/local77b01da1 now consume nativev0.19.1-2, owner0b15fb34ef1e9542eefca106c4c832ac852ffed1/upstream7a03724cece417f1724c923b3d527b4319730841. Marker admission/software-only Vulkan refusal first shipped0.19.1; native raw-prompt/template/probe/token-accounting consumer fixes first shipped0.19.3 because0.19.2 never reached pub.dev. No new owner release, stable pin implementation or carry retirement.
Raw stable stays19.1. Inspected main01a0b3fd8ee9b57c404b0d85c4f7b1095d14bf5a adds16 commits beyond yesterday; all below are absent owner/public:
No new c/ or JS API delta in these16 commits, but the existing raw C API1.1 versus pinned1.0 migration remains. Select an exact owner candidate, re-port carries, verify headers/exports/ABI and qualify affected state/constraints/MTP/CPU/GPU/Omni paths before new artifacts, consumer mappings/checksums/SwiftPM/docs. npm stable19 stays; nightly advances20261109. Bridge83/sourcecb6383fb/llamacd959bae and manifestae6f4884 are unchanged.
Core#1880/#1891 are unmerged Web consumer candidates on the existing npm19 pin, not new upstream stop-cause APIs. No new owner/bridge workflow failure/stall or CSP delta; intentionally manual release flows are unchanged. No source/pin/workflow/model/device jobs by this scan.
leehack commentedon Nov 11, 2026
2026-11-11 delivery: owner v0.19.1-3,
ed8ffe332441d24157475d9514bff9a601bb615b/ upstream7a03724cece417f1724c923b3d527b4319730841, published Nov10 20:25 UTC, is consumed by public core/Apple 0.19.5, main/local4ecd129a. Manifest SHA25695aa8b24c9ca967be9a6f627191278a6e41926ddba58979476b378c4756c41e9; C API1.0.0/callback2/in-process marker1 and six carries unchanged. #118/consumer#1913 remove unused Apple Metal payload; primary runtime inputs/ABI are unchanged. This is not physical-iPhone GPU qualification.Native strict JSON Schema's wider consumer admission first ships0.19.5 using existing setters, not a new owner ABI; core#174's published-subset checkpoint preserves hardware, regex and Web gates. Web tool/loop policy first ships0.19.4 on existing npm19, with conservative EOS-at-cap truncation, not a new terminal-cause API (#919).
Raw stable remains19.1. Inspected main61fd1385 adds31 commits since yesterday's01a0b3fd; npm stable19/nightly20261109 remain unchanged. New raw-only work:
No c/ ABI delta in these31 commits; earlier raw1.1-versus-consumed1.0 migration and carry re-porting still precede raw adoption, bindings, capability/configuration mapping, checksums/SwiftPM and validation. #70 clone and #99 LoRA limitations are unchanged; fixture export is not LoRA runtime support.
Owner candidate#119,
d176e4eb, follows core#1911 for further size reduction. Its qualification was active, not published/failed/stalled. Bridge83 remains immutable/sourcecb6383fb/llamacd959bae; no new owner/bridge release failure observed. No automatic stable repin or duplicate ticket is needed. Existing priority/acceptance unchanged; no source/pin/workflow/model/device execution by this scan.Full-pin model/ancestry clarification (7a03724c → 61fd1385): histories diverge, with 241 main-only/7 stable-only commits, not 241 new capabilities. MiniCPM-o4.5 Any2Any is the only newly named family in the net Omni model table: text/image/audio frontend, Qwen3-8B LLM, CosyVoice2/Token2Wav, 16kHz input/24kHz output; owner Omni ABI/API and model/lifetime qualification precede Dart support. Whisper base/small/medium/int8 aliases are variants. Qwen3-TTS c31744fe changes INT8 MTP/per-head and codec signatures while retaining legacy detection; Gemma4 26B/31B metadata and Qwen3.5 GPU changes are configuration/compatibility, not new registrations. Parakeet, Whisper tiny, Qwen3-ASR, Moonshine, Kokoro, Qwen3-TTS and Bonsai-FLUX2/FLUX2-Klein were already registered at the stable pin; no public support is inferred from that presence. Core speech stays #1161; Web-media canonical owner is #1789, with #1153 closed as duplicate. The Tensor API executor headline in 9ffe5f12 supplies only empty BUILD selects, not an implemented/exported consumable backend.
leehack commentedon Nov 12, 2026
2026-11-12 delivery: v0.19.1-4, source
5da99205b1fd93acd9ca518d77bf7da5bc38ffce/ upstream7a03724cece417f1724c923b3d527b4319730841, is public and consumed by core/all Apple companions0.19.6, main/localfb7ca7d5. Manifest SHA256a75c1957c726926c8ac0fc0af9d985f054563d845fa7ca71f2a92309161fa868; six carries and C API1.0/callback2/ASR1/marker contracts unchanged. #119 qualification19/19 and publication succeeded; consumer#1927 ships the four-target SwiftPM topology. This is packaging/inventory reduction, not a runtime-source/ABI gain or physical-iPhone GPU qualification. Core#1911 delivery checkpoint records size/companion floors; no additional repin/code work is needed to consume it.Raw stable remains19.1; main0c54891e is21 commits since yesterday61fd1385. Stable/main histories diverge262 main-only/7 stable-only—not262 capabilities. Material raw-only gates:
No new family today. MiniCPM-o4.5 Any2Any remains the full-pin raw-only family addition; Whisper registrations/Qwen3-TTS layouts are variants/components. LFM2.5-Audio Any2Any#4522 remains unmerged. Open proposals4562(C API1.2 channels),4563(NPU RNG/state),4559(cache sync),4528(cancel/drain),4533(CPU media eviction) are not delivered. #70/#99/#174 acceptance unchanged; no new hardware/regex/Web closure credit.
Bridge83 remains immutable (assets44aa84a8/sourcecb6383fb/llamacd959bae, manifestae6f4884), with no new owner/bridge failure/stall or update PR. Core1863 closed as documented raw-prompt exception, and1802 as documented compat-Wasm limitation—not upstream API fixes. Current core1931 chat trimming is main-only, not public19.6. Preserve existing priority/scope; no source/pin/workflow/device execution by this scan.
leehack commentedon Nov 13, 2026
2026-11-13: latest owner v0.19.1-4, source
5da99205b1fd93acd9ca518d77bf7da5bc38ffce/ upstream7a03724cece417f1724c923b3d527b4319730841, remains pinned by public0.19.8, local768feb72 and maina2a5cf29. Manifest independently hashesa75c1957c726926c8ac0fc0af9d985f054563d845fa7ca71f2a92309161fa868; six carries/C API1.0/callback2/ASR1/marker unchanged. No new owner release/failure/stall or automatic pin work.Raw stable remains19.1. Main4b63acd7 adds12 since0c54891e; histories diverge274 main-only/7 stable-only, not274 capabilities. New raw-only gates:
FunctionGemma GPU-LoRA Colabs are training/conversion examples; raw resource_manager still rejects new scoped text LoRA. Qualify initial text LoRA: upstream session path setter does not establish executor support #99 unchanged.
No new family today. Full-pin MiniCPM-o4.5Any2Any remains raw-only; Whisper/Qwen3-TTS additions are variants/components. npm remains stable19/nightly20261109; open4522/4528/4533/4559/4562/4563 are unmerged. Prior raw1.1/consumed1.0 ABI/carry migration remains before artifact, checksums/SwiftPM, configuration/probes/docs and real-model/device adoption.
Separate Web delivery: immutable bridge84, assets0a3c45f2/source dc359398/llamacd959bae, manifest55abeb377597148156059a8ee5400f2314c6254ad91b57db65b709e304c0dea0, is public through core0.19.8 for budget grammar control. Owner qualification/publication passed; later bridge main is docs-only. No additional runtime republish is needed. Core1971/1977 media warmup fix and1979 forwarding through1985 are consumer lanes, not a new LiteRT or bridge capability release; publication/hardware subsets remain separate. P1 owner51 and other unchanged priorities are NOT downgraded by consumer fallback. No source/pin/workflow/device execution by this scan.