[skip ci][recipe] draft vllm-omni recipes

[hsliuustc0106]

PLEASE FILL IN THE PR DESCRIPTION HERE ENSURING ALL CHECKLIST ITEMS (AT THE BOTTOM) HAVE BEEN CONSIDERED.

Purpose

resolve #2645

Test Plan

N.A.

Test Result

N.A.

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan. Please provide the test scripts & test commands. Please state the reasons if your codes don't require additional test scripts. For test file guidelines, please check the test style doc
• The test results. Please paste the results comparison before and after, or the e2e results.
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model. Please run mkdocs serve to sync the documentation editions to ./docs.
• (Optional) Release notes update. If your change is user-facing, please update the release notes draft.

BEFORE SUBMITTING, PLEASE READ https://github.com/vllm-project/vllm-omni/blob/main/CONTRIBUTING.md (anything written below this line will be removed by GitHub Actions)

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[Copilot]

Pull request overview

Introduces a new top-level recipes/ area intended to host community-maintained “known-good setup” runbooks (organized by model vendor) to help users run model X on hardware Y for task Z, aligned in spirit with vllm-project/recipes.

Changes:

• Added recipes/README.md describing the intended structure and linking to the template.
• Added recipes/TEMPLATE.md providing a standardized recipe format for contributors.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
recipes/README.md	Documents the purpose and proposed vendor-based layout for community recipes.
recipes/TEMPLATE.md	Adds a Markdown template to standardize recipe content (env/command/verification/notes).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In this template, the sub-sections (Environment/Command/Verification/Notes) are at the same heading level as the hardware configuration ("### 1x A100 80GB"), which flattens the structure and makes it harder to render/navigate. Consider nesting these under the hardware config (e.g., make them one level deeper) so each hardware section is self-contained.

[Copilot]

The PR description indicates it "resolve #2645", but the RFC’s scope/success criteria include adding vendor-organized recipe docs (e.g., recipes/Qwen/Qwen3-Omni.md, etc.). This PR currently adds only a template and README; either add at least one initial recipe under a vendor directory, or adjust the PR description/issue-closing keyword so it doesn’t prematurely close the issue.