record(MODEL-MATRIX): row the 7 recipe architectures that had none (#609, #610)

[localai-bot]

Replaces #620 (same tree, clean history — see "Why a new PR" at the bottom).

Records only. No src/ or include/ change.

An audit of the 157 official model recipes at vllm-project/recipes 86c7777a,
joined to each model's HF config.json architectures and then to
.agents/model-matrix.md, found architecture strings with no row at all.
Seven are added here at INVENTORIED.

Seven, not eight, and not nine

#609 and #610 say two and seven; their own tables enumerate two and six.
Reproducing the audit independently — 157 recipes → 157 config rows → join —
returns exactly eight distinct architectures. The unit is the
architecture, and MossTTSDelayModel alone is reached by four recipes.

Of those eight, Qwen3_5MoeForCausalLM is already rowed by #490 / PR #601
under the identical stable ID MODEL-TEXT-qwen3-5-qwen3-5-moe-for-causal-lm
(verified with gh pr diff 601). Two branches adding the same keyed row merge
with no conflict and define it twice, silently. That row is left to its
owner; seven land here.

Row ID	Architecture	Recipes
MODEL-TEXT-bailing-moe-v3-bailing-moe-v3-for-causal-lm	BailingMoeV3ForCausalLM	Ling-3.0-flash
MODEL-MM-moss-tts-moss-tts-delay-talker-for-generation	MossTTSDelayModel	MOSS-TTS, MOSS-TTSD-v1.0, MOSS-SoundEffect, MOSS-VoiceGenerator
MODEL-MM-moss-tts-moss-tts-realtime-talker-for-generation	MossTTSRealtime	MOSS-TTS-Realtime
MODEL-MM-qwen3-tts-qwen3-tts-talker-for-conditional-generation	Qwen3TTSForConditionalGeneration (+ Talker alias)	Qwen3-TTS-12Hz-1.7B-CustomVoice
MODEL-MM-higgs-audio-v3-higgs-audio-v3-talker-for-conditional-generation	HiggsMultimodalQwen3ForConditionalGeneration (+ Talker alias)	higgs-audio-v3-tts-4b
MODEL-MM-voxtral-realtime-voxtral-realtime-for-conditional-generation	VoxtralRealtimeForConditionalGeneration (target-pending)	Voxtral-Mini-4B-Realtime-2602
MODEL-MM-bailing-mm-native-bailing-mm-native-for-conditional-generation	BailingMMNativeForConditionalGeneration (target-pending)	Ming-omni-tts-0.5B

Why dropping the Qwen row is right, not just deconflicting

Qwen3_5MoeForCausalLM is neither an alias of
Qwen3_5MoeForConditionalGeneration nor a new port. The class already exists
at our pin (qwen3_5.py:381; main :443) and is exactly what the multimodal
class builds as its own text tower:
self.language_model = Qwen3_5MoeForCausalLM(...) at qwen3_5.py:643 (pin) /
:724 (main). vLLM main only added a registry entry (registry.py:203)
exposing that existing backbone standalone — same module, different class,
different task category, no vision tower, no MM processor.

Which is exactly why registering it, as #601 does, is the correct treatment,
and an INVENTORIED row here would have understated it.

BailingMoeV3ForCausalLM is a new module, not a class rename: V2.5
(bailing_moe_linear.py, 821 lines at the pin) pairs MLA with Bailing linear
attention; V3 (bailing_moe_v3.py, 1495 lines on main) keeps MLA and swaps the
linear arm for Kimi Delta Attention, adds per-projection causal conv1d,
grouped-topk MoE via config.n_group, a clamped SwigluStepAndMul, an fp8
quant-config hook, and refuses a checkpoint without no_kda_lora=True.

The two target-pending rows record what was searched rather than an invented
anchor: the exact config.json strings appear in none of the pinned registry,
any of the ten dictionaries of main's registry.py, vllm-omni's
_OMNI_MODELS, or vllm-omni's supported_models.md. Near misses are named
(VoxtralRealtimeGeneration is registered at the pin and already has its own row;
vllm-omni carries a BailingMM2NativeForConditionalGeneration alias — note the
2) without asserting either is the target.

Counts

Re-derived from the file with the checker's own parser, not by arithmetic:
369 rows — INVENTORIED 321, PARTIAL 20, ACTIVE 9, SPIKE 7, BLOCKED 5,
READY 3, DONE 3, GATING 1, and 48 non-INVENTORIED. Header prose follows:
326 at the pin + 10 beyond = 336, long tail 291, engaged 45 unchanged.
check-agent-record's MODEL pin 362 → 369.

The at-the-pin model inventory is unchanged (324/373/356/310/261): none of the
seven is at the pin, so like the MuseGlimmer, KimiK3 and MiniMaxH3DiT rows they
spell module and class as separate fields instead of the colon-pair form
check_model_invariants counts. Existing convention — no checker expectation
was widened.

One pre-existing error corrected while the block was open: the caption read
"the 49 non-INVENTORIED rows" where the file has, and had, 48.

Mutation evidence (pr-size contract)

Two tests added. What each catches was measured, not assumed; tree restored
byte-for-byte after each mutation.

Mutation	Caught by
A. Delete a pinned row + bump the count to hide it	Both new tests; none of the 49 pre-existing. Also the CLI — but via the roadmap dangling-reference check, not the ratchet, and only because that row is intake-linked
B. Give an out-of-repo row an at-the-pin colon-pair anchor	New inventory test and the CLI's own check_model_invariants. No pre-existing test
C. Delete an unpinned new row (Higgs — not intake-linked, not named by the ratchet test) + bump the count	ONLY test_beyond_pin_rows_stay_out_of_the_at_pin_model_inventory. CLI prints agent record OK: ... MODEL=368; every pre-existing test passes. check-model-checklist still catches it via the rollup

Stated plainly: B is a third pin on something the CLI already defends (as its
Windows precedent also is). C is a defect only the new test catches.

Evidence

$ python3 scripts/check-model-checklist.py
OK: architecture-support checklist matches the detailed row states.

$ python3 scripts/check-agent-record.py
agent record OK: ENGINE=152 MODEL=369 QUANT=82 KERNEL=51 BACKEND=81

$ python3 scripts/check-pr-size.py --base origin/main --head HEAD ...
OK: every explicit path class is within its review budget.

$ python3 scripts/check-doc-checkpoint.py --base origin/main --head HEAD
OK: public documents match the claims this change makes.

scripts/agent-preflight.sh --staged → exit 0, 71 gates ok, zero failures.

Why a new PR instead of pushing to #620

#620's first commit changed a feature_surface without docs/FEATURES.md in
that same commit. check-doc-checkpoint is per-commit by design and has no
exemption mechanism ("that is precisely how the old gate grew six hardcoded
escape hatches"), so no later commit could clear it — I verified that directly.
The only remedies were rewriting published history or clean history on a fresh
branch. This protocol takes no force variant, so: fresh branch. The tree here
is byte-identical to the verified #620 head.

Also filed #618 — test_cpu_x86_llamacpp_floor's contended-leg case went red at
loadavg 63 and green at 21.9 on the same tree; it races the quiet-window gate and
fails toward a verdict on whatever diff is in flight. Filed, not fixed here.

Closes #609.
Closes #610.

[localai-bot]

Finding accepted and fixed in `d6cdd88b2` — added as a commit, no history rewrite (fast-forward `cbace19bc..d6cdd88`).

You were right that this was more than a typo. `test_model_row_ratchet_is_load_bearing`'s docstring is the prose explanation of why the ratchet exists, and it contradicted its own constant one screen above the new test that already said `362 -> 369`. The next person to re-pin reads the docstring.

Grep results, both files, as asked — not eyeballed.

Before:

$ grep -n "370" tests/scripts/test_agent_record.py
260:        eight recipe architectures that had no row at all took it 362 -> 370
$ grep -ni "eight" tests/scripts/test_agent_record.py
260:        eight recipe architectures that had no row at all took it 362 -> 370
$ grep -n "370" scripts/check-agent-record.py
(none)

After:

$ grep -n "370" tests/scripts/test_agent_record.py        -> (none)
$ grep -ni "eight" tests/scripts/test_agent_record.py     -> (none)
$ grep -n "370" scripts/check-agent-record.py             -> (none)
$ grep -niE "\beight\b" scripts/check-agent-record.py
52:    # of an invented anchor. SEVEN, not eight: the audit's eighth architecture

That last one is deliberate and load-bearing — it records why the audit's eighth architecture is left to #490 / PR #601. The bare `grep -ni eight` on the checker also matches substrings inside `weight`/`weighted` on lines 62/94/111/135/144/165, which is why the whole-word form is the honest check.

I also swept every line this branch adds rather than just those two files, since a stale number could have hidden in the matrix or roadmap:

$ git diff origin/main -- <the 5 changed files> | grep -E "^\+" | grep -nE "\b370\b|\b322\b|\b337\b|\b292\b|\beight\b"
46:+    # of an invented anchor. SEVEN, not eight: the audit's eighth architecture

One hit, the intended one. The corrected values appear consistently across added lines: `369` x5, `336` x2, `321`, `291`, `seven` x6. Both docstrings now agree:

260:        seven recipe architectures that had no row at all took it 362 -> 369
286:        """The #609/#610 rows and the 362 -> 369 bump are one semantic change.

Gates re-run afterwards under the exact CI invocations:

$ python3 scripts/check-pr-size.py --base origin/main --head HEAD --branch row/model-matrix-recipe-backfill-clean --pr-number 625
OK: every explicit path class is within its review budget.

$ python3 scripts/check-agent-record.py
agent record OK: ENGINE=152 MODEL=369 QUANT=82 KERNEL=51 BACKEND=81

$ python3 scripts/check-doc-checkpoint.py --base origin/main --head HEAD
OK: public documents match the claims this change makes.

$ python3 scripts/check-model-checklist.py
OK: architecture-support checklist matches the detailed row states.

$ python3 tests/scripts/test_agent_record.py
Ran 51 tests in 10.423s
OK

`scripts/agent-preflight.sh --staged` -> exit 0, 71 gates ok, zero failures.