Follow-up to #235 — the PRISM/APEX presets exercised (model, engine, KV)
combos the profile catalog didn't know about, reddening test-profiles-compat
and test-diagnose-profile (caught by the pre-tag FULL-suite run, which the
narrower #235 gate subset had missed).
- engines/llama-cpp-mainline.yml: supported_model_families += qwen3-next-moe
(the 35b-a3b APEX MoE; llama.cpp serves the MoE GGUF — the family list was
just incomplete). Fixes constraint C10 for the 3 APEX entries.
- hardware/*.yml (all 9): supported_kv_formats += q5_0, q8_0 — the llama.cpp
KV quants the engine already lists but no hardware profile did, so the q8_0
presets (prism-pro-dq-dual-vision, apex-mtp-compact-long, apex-mtp-quality-dual)
failed C5 "kv not supported by hardware". q5_0/q8_0 are software KV quants
that work on any CUDA card (laurimyllari runs q8_0 on a 4090).
- patches.yml: register the APEX chat-template (apex-qwen-chat-template) with a
symmetric-protocol drift_guard — resolves the orphan #235 introduced into
test-patch-attribution.
Validation: test-profiles-compat + test-diagnose-profile PASS. APEX patch-
attribution orphan resolved (only the 2 PRE-EXISTING sglang orphans remain =
the v0.8.5 baseline). Full suite 29/34; the 5 remaining fails are all
pre-existing-at-v0.8.5 or test-isolation, NONE from the v0.8.5..master range:
generate-compose (pre-existing), setup-picker (mock 5090 rig), submit-bench
(0 fixtures), loop-input (test-hwdetect .pull-captures cross-contamination —
passes in isolation). Leak-clean.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
aa2a965bb9