clm-0110
On the v0.6.10 strix-halo fork under Vulkan/RADV (build 2586f6edd), Qwen3.6-35B-A3B-MTP UD-Q4_K_M with reasoning OFF recovers MTP n2 capability that build 7077abb-upstream-on-ROCm0 destroyed. This is a STACK effect, not a build-only change: AB ran ggml-org 7077abb on ROCm0/gfx1151 (cfg-0144/0145, run-0568/0569/0570/0571), while this retest ran the Nathanw1014 fork on Vulkan/RADV (cfg-0149/0150, run-0575..0578) — repo, backend and build all changed together, so the comparison is strictly "v0.6.10-fork-on-Vulkan vs 7077abb-upstream-on-ROCm0", never a build-only claim. Within v0610, native-MTP n2 (--spec-type draft-mtp --spec-draft-n-max 2) scored 17/26 (mean 0.65385) vs plain 22/26 (mean 0.84615); Fisher exact two-sided n2-worse p=0.1994 — n2 is NOT significantly worse than plain on this stack. Against the ORIGINAL AB n2 failure, n2 17/26 vs AB n2 0/26 (run-0571) p≈2.8e-07 (Fisher two-sided) — MTP n2 capability destroyed on 7077abb is recovered on v0.6.10. The empty-turn/agent-spam mechanism is resolved at the mechanism level: all 26 v0610 n2 terminations were user_stop with 0 too_many_errors, 0 max_steps, 0 empty-assistant and 1 empty-argument tool call (tool_call_messages 192), versus AB n2's 415 tool-call + 21 too_many_errors + 2 max_steps spam on run-0571. Scope is strictly qwen35moe target, UD-Q4_K_M, reasoning-off, n_max=2 only. NO DFlash2, stock-MTP, n_max>=4, reasoning-on, alt-model, alt-backend, or production-throughput claim is made or inherited.