con-0014

Primary-source runtime-watch record: Nathanw1014/strix-halo-llamacpp v0.6.11, published 2026-08-24, fixes the fork-only image-request regression introduced by the fork's v0.6.8 DFlash M-RoPE change. For a position-sharing draft-mtp context, the old token-space trim left the draft behind the target after an image span and led to inconsistent M-RoPE positions, llama_decode failure, and HTTP 500. Commit 0eb528051a56f34567312ce63ab4e14a3fc71d89 records whether a draft cache is dense-row indexed: DFlash/DSpark retain token-space trimming, while draft-mtp and eagle3 use target position space. The release's gfx1151 Vulkan/RADV smoke on Qwen3.8-27B-UD-Q6_K_XL plus mmproj-F16 reports that draft-mtp n_max=3 image requests now return HTTP 200 with speculation remaining active; its DFlash image and speculation-off controls are unchanged. The release asset digest is sha256:a4306edefdefb2eff925cbc43cbf32cd42cf07c00e06011e906957217bf1ddad and MANIFEST.txt identifies the portable payload source as 0eb528051. This is a fork-vendor functional-correctness report, not a HaloBench benchmark: the release explicitly says its smoke checks are not BENCHMARKS.md throughput and makes no throughput claim. It has no text-only agent outcome, guard result, capability score, energy join, or served-path/floor pair. The regression never applied to upstream llama.cpp or to fork configurations with speculation off, so it cannot rebaseline existing text-only Qwen3.8 throughput/capability records or replace their recorded v0.6.10/stock runtime provenance. A future vision/MTP prep card is justified only as a separately scoped, on-box validation of this exact payload with multimodal request controls and the house guard; it is not a reason to dispatch a benchmark or change the production pick now.