docs: remove recipe coverage registry

Signed-off-by: Hongsheng Liu <liuhongsheng4@huawei.com>
2026-08-10 12:47:40 +08:00
1 parent d10bf78c60
commit 159dceaf65
@@ -1,73 +0,0 @@
-# SPDX-License-Identifier: Apache-2.0
-# SPDX-FileCopyrightText: Copyright contributors to the vLLM project
-
-# This registry is keyed by an exact Hugging Face checkpoint and task. A
-# Supported Models row may cover several checkpoints, but coverage entries must
-# be split whenever the example or recipe differs.
-version: 1
-
-# The registry is incrementally audited. An absent entry means that coverage
-# has not been audited yet; it is not evidence that no recipe exists. Do not
-# infer recipe coverage from the implementation or hardware columns in
-# supported_models.md.
-entries:
-  - model: Qwen/Qwen3-Omni-30B-A3B-Instruct
-    task: omni-serving
-    examples:
-      - docs/user_guide/examples/offline_inference/qwen3_omni.md
-      - docs/user_guide/examples/online_serving/qwen3_omni.md
-    recipe:
-      status: repository
-      repository_path: recipes/Qwen/Qwen3-Omni.md
-      hardware: [nvidia]
-
-  - model: Qwen/Qwen-Image
-    task: text-to-image
-    examples:
-      - docs/user_guide/examples/offline_inference/text_to_image.md
-      - docs/user_guide/examples/online_serving/text_to_image.md
-    recipe:
-      status: published
-      published_url: https://recipes.vllm.ai/Qwen/Qwen-Image
-      repository_path: recipes/Qwen/Qwen-Image.md
-      hardware: [nvidia]
-
-  - model: Qwen/Qwen-Image-2512
-    task: text-to-image
-    examples:
-      - docs/user_guide/examples/offline_inference/text_to_image.md
-      - docs/user_guide/examples/online_serving/text_to_image.md
-    recipe:
-      status: repository
-      repository_path: recipes/Qwen/Qwen-Image-2512.md
-      hardware: [nvidia]
-
-  - model: Qwen/Qwen3-TTS-12Hz-1.7B-CustomVoice
-    task: text-to-speech
-    examples:
-      - docs/user_guide/examples/offline_inference/text_to_speech.md
-      - docs/user_guide/examples/online_serving/text_to_speech.md
-    recipe:
-      status: published
-      published_url: https://recipes.vllm.ai/Qwen/Qwen3-TTS-12Hz-1.7B-CustomVoice
-      repository_path: recipes/Qwen/Qwen3-TTS.md
-      hardware: [nvidia]
-
-  - model: bosonai/higgs-audio-v3-tts-4b
-    task: text-to-speech
-    examples:
-      - docs/user_guide/examples/online_serving/text_to_speech.md
-    recipe:
-      status: published
-      published_url: https://recipes.vllm.ai/bosonai/higgs-audio-v3-tts-4b
-      repository_path: recipes/BosonAI/Higgs-Audio-V3-TTS.md
-      hardware: [nvidia]
-
-  - model: MiniMaxAI/MiniMax-H3
-    task: video-audio-generation
-    examples: []
-    recipe:
-      status: published
-      published_url: https://recipes.vllm.ai/MiniMaxAI/MiniMax-H3
-      repository_path: recipes/MiniMaxAI/MiniMax-H3.md
-      hardware: [nvidia, amd]
@@ -96,42 +96,17 @@ th {
 | `ErnieImagePipeline` | ERNIE-Image | `baidu/ERNIE-Image`, `baidu/ERNIE-Image-Turbo` | ✅︎ | ✅︎ | ✅︎ | ✅︎ | — |
 |`HiDreamImagePipeline` | HiDream-I1-Full | `HiDream-ai/HiDream-I1-Full` | ✅︎ | ✅︎ | | | — |

-The `Recipe` column links the exact checkpoint/task entry from
-[`recipe_coverage.yaml`](https://github.com/vllm-project/vllm-omni/blob/main/docs/models/recipe_coverage.yaml).
-`Published` is preferred when a corresponding `recipes.vllm.ai` page exists;
-otherwise the link points to the repository recipe. `—` means that the exact
-checkpoint/task mapping has not been audited yet.
+The `Recipe` column links the corresponding deployment recipe. `Published` is
+preferred when a corresponding `recipes.vllm.ai` page exists; otherwise the
+link points to the repository recipe. `—` means that no recipe link has been
+added for that model row yet.

 For rows with an audited recipe link, the hardware checkmarks reflect hardware
 explicitly documented in that recipe. Other rows retain the implementation
-support metadata until their recipe coverage is audited.
+support metadata until their recipe is audited.

 ✅︎ indicates the model is supported on that backend. Empty cells mean not listed as supported on that backend.

-## Recipe and Example Coverage
-
-The table above describes implementation and backend support. It does not
-imply that a model has a validated deployment recipe.
-
-Recipe and example coverage is tracked per exact Hugging Face checkpoint and
-task in the machine-readable
-[`recipe_coverage.yaml`](https://github.com/vllm-project/vllm-omni/blob/main/docs/models/recipe_coverage.yaml).
-The registry is populated as coverage is audited and is the source of truth
-for mapping exact checkpoints and tasks to links. Recipe files under
-[`recipes/`](https://github.com/vllm-project/vllm-omni/tree/main/recipes) remain
-the source of truth for commands and validation details. It uses the following
-link precedence:
-
-1. `published`: link to the published `recipes.vllm.ai` page.
-2. `repository`: link to the in-repository recipe until a published page exists.
-3. `no_validated_recipe_yet`: show `No validated recipe yet` only when that
-   result has been explicitly audited.
-4. A checkpoint/task without an entry: coverage has not been audited yet.
-
-Split entries whenever checkpoints, tasks, examples, or validation evidence
-differ. A single Supported Models row may therefore map to multiple registry
-entries.
-
 <sup>H3</sup> MiniMax H3 AMD GPU support is validated on gfx942 (MI300X) and
 gfx950 (MI350) in BF16, using the AITER `FLASH_ATTN` diffusion attention backend.
 Other AMD SKUs (e.g. MI325X) are not listed until their