llama.cpp effort debate spans Qwen3, TurboQuant

The split is real: new model support usually means architecture-specific integration work, while TurboQuant-style features are more about quantization and backend plumbing. Commit count alone is a weak proxy, but GitHub history can still show which changes were broad, review-heavy, and bug-prone.

• –Search PRs and commits by feature name, then compare diff stats, files touched, review comments, and follow-up fixes.
• –Qwen3-related work in llama.cpp has involved parser/template/architecture changes plus bug fixes, which points to broader integration effort.
• –TurboQuant work has landed as new ggml types and cache-path changes, but it still ripples across CPU/CUDA/Vulkan backends and CLI wiring.
• –Best practical query pattern: `gh search prs --repo ggml-org/llama.cpp "Qwen3"` or `git log --grep=Qwen3 --stat`, then compare against `TurboQuant`, `TBQ3_0`, or `TQ3_0`.