tzhouam · Sep 5, 2026 · Sep 3, 2026 · Sep 3, 2026 · Sep 3, 2026 · Sep 3, 2026
diff --git a/adapters/vllm_omni/manifest.yaml b/adapters/vllm_omni/manifest.yaml
@@ -72,14 +72,14 @@ modules:
     wave: 1
     risk: high
   model_executor:
-    local_paths: [vllm_omni/model_executor/]
+    local_paths: [vllm_omni/model_executor/, vllm_omni/experimental/, vllm_omni/model_extras/, vllm_omni/transformers_utils/]
     upstream_paths: [vllm/model_executor/]
     test_paths: [tests/model_executor/, tests/diffusion/, tests/e2e/offline_inference/]
     import_check: "from vllm_omni.model_executor.models.registry import *; print('Model Executor imports OK')"
     wave: 1
     risk: high
   input_output:
-    local_paths: [vllm_omni/inputs/, vllm_omni/outputs/, vllm_omni/engine/async_omni_engine.py, vllm_omni/engine/orchestrator.py, vllm_omni/engine/serialization.py, vllm_omni/engine/stage_init_utils.py, vllm_omni/engine/stage_engine_core_client.py, vllm_omni/engine/output_processor.py, vllm_omni/request.py]
+    local_paths: [vllm_omni/inputs/, vllm_omni/outputs/, vllm_omni/utils/mm_outputs.py, vllm_omni/data_entry_keys.py, vllm_omni/engine/async_omni_engine.py, vllm_omni/engine/orchestrator.py, vllm_omni/engine/serialization.py, vllm_omni/engine/stage_init_utils.py, vllm_omni/engine/stage_engine_core_client.py, vllm_omni/engine/output_processor.py, vllm_omni/request.py]
     upstream_paths: [vllm/inputs/, vllm/v1/engine/input_processor.py, vllm/v1/engine/output_processor.py, vllm/v1/request.py]
     test_paths: [tests/entrypoints/test_omni_new_request_data.py, tests/engine/test_async_omni_engine_input.py, tests/test_outputs.py]
     import_check: "from vllm_omni.inputs.data import *; from vllm_omni.inputs.preprocess import *; from vllm_omni.engine.async_omni_engine import AsyncOmniEngine; from vllm_omni.engine.orchestrator import Orchestrator; from vllm_omni.engine.serialization import serialize_additional_information; print('Input/Output imports OK')"
@@ -92,13 +92,13 @@ modules:
     wave: 1
     risk: high
   online_serving:
-    local_paths: [vllm_omni/entrypoints/]
+    local_paths: [vllm_omni/entrypoints/, vllm_omni/engine/]
     upstream_paths: [vllm/entrypoints/]
     test_paths: [tests/entrypoints/test_async_omni.py, tests/entrypoints/test_async_omni_diffusion_config.py, tests/entrypoints/openai_api/]
     import_check: "from vllm_omni.entrypoints.omni import Omni; from vllm_omni.entrypoints.async_omni import AsyncOmni; from vllm_omni.entrypoints.openai.api_server import omni_run_server; from vllm_omni.entrypoints.openai.serving_speech import ServingSpeech; from vllm_omni.entrypoints.cli.serve import OmniServeCommand; print('Online Serving imports OK')"
     wave: 1
   model_config:
-    local_paths: [vllm_omni/config/, vllm_omni/engine/arg_utils.py]
+    local_paths: [vllm_omni/config/, vllm_omni/deploy/, vllm_omni/engine/arg_utils.py]
     upstream_paths: [vllm/config/, vllm/engine/arg_utils.py]
     test_paths: [tests/entrypoints/test_stage_utils.py, tests/metrics/test_stats.py]
     import_check: "from vllm_omni.config.model import OmniModelConfig; from vllm_omni.engine.arg_utils import OmniEngineArgs; print('Model Config imports OK')"
@@ -143,6 +143,19 @@ modules:
   quantization:
     local_paths: [vllm_omni/quantization/]
     wave: 1
+  runtime_patch:
+    local_paths: [vllm_omni/patch.py]
+    test_paths: [tests/diffusion/test_inductor_divisibility_patch.py]
+    wave: 1
+    risk: high
+  # Filesystem-backed immutable host artifacts have process-wide lock, lease,
+  # durability, and fallback contracts; keep this owner explicit rather than
+  # letting generic runtime scopes silently omit it.
+  host_weight_runtime:
+    local_paths: [vllm_omni/host_weight_runtime/]
+    test_paths: [tests/host_weight_runtime/]
+    wave: 1
+    risk: high
   sampling:
     local_paths: [vllm_omni/sample/]
     wave: 1
@@ -158,8 +171,16 @@ modules:
     test_paths: [tests/benchmarks/test_serve_cli.py]
     import_check: "from vllm_omni.benchmarks.serve import main; from vllm_omni.entrypoints.cli.benchmark.serve import OmniBenchmarkServingSubcommand; print('Benchmarks imports OK')"
     wave: 2
+  fullduplex:
+    local_paths: [vllm_omni/experimental/fullduplex/]
+    test_paths: [tests/benchmarks/duplex/, tests/e2e/features/fullduplex/]
+    import_check: "from vllm_omni.experimental.fullduplex.client import RealtimeDuplexClient; print('Full-duplex client imports OK')"
+    wave: 2
 
 review_routes:
+- prefix: vllm_omni/patch.py
+  owner: tooling
+  doc: repos/vllm-omni/tooling/rules.md
 - prefix: vllm_omni/config/
   owner: config
   doc: repos/vllm-omni/components/configuration/rules.md

diff --git a/adapters/vllm_omni/release_baseline.yaml b/adapters/vllm_omni/release_baseline.yaml
@@ -2,25 +2,25 @@ schema_version: 1
 
 upstream:
   repository: vllm-project/vllm-omni
-  previous_audited_sha: 5d44868e918ecf9d3a6f1158c45acfad5989e1a7
-  audited_ref: v0.26.0rc1
-  audited_sha: 807db6efd70ff2e9b55a63d6e1b0530e2b74f8f2
+  previous_audited_sha: ae57e406fd02516ef5ee8cd40a1458328e13a2a5
+  audited_ref: main
+  audited_sha: 1e74807c356be5cba4239faae7c38763fe1a44be
 
 # These fingerprints are generated from sorted registry/deploy inventories.
 # They make the baseline exact without duplicating hundreds of entries here.
 inventories:
   autoregressive:
-    count: 72
-    sha256: 79afac742125003b8d65a02e0e6b53398c4fc5f1c6e765fa8e1eb31f74871195
+    count: 89
+    sha256: cd6b56fe44e88ca35e4d2c961a00cf7a257695ca193e8279d6562eb72ca58fc4
   diffusion:
-    count: 61
-    sha256: f5c0b782cb98f20a9c7c77b696fda620a12d0899fd9e8abc9ccb696fe0c457e1
+    count: 65
+    sha256: 6107384ad499e668c1ed3690d740b7be816c900c504f244dce557ef51a257f2a
   pipelines:
-    count: 46
-    sha256: ce4f6edb8748e030f04bf7a6fe038231453cd1cd75f64311c898acff8c14b14b
+    count: 59
+    sha256: 4f012fb016221c2115520b16577bb69be03e84987122729bea696c14e5bca42f
   deploy_yamls:
-    count: 71
-    sha256: fb4c591580262a2dc8d03dd8c7fd681d98486f31007696d56adf349c24c25147
+    count: 89
+    sha256: 7895ed1c963b0d2a4afedda6a45c422288973a50c73a1255d271a8beefe0a39f
 
 # Structural review owners for changed upstream paths. This is deliberately
 # separate from manifest.modules: changing that runtime map alters rebase fan-out.
@@ -33,6 +33,7 @@ path_owners:
   - .github/
   - docker/
   configuration:
+  - collect_env.py
   - vllm_omni/config/
   - vllm_omni/deploy/
   diffusion:
@@ -43,8 +44,8 @@ path_owners:
   - .claude/skills/
   - docs/
   - examples/
+  - mkdocs.yml
   - recipes/
-  - realtime_video_prompt_interaction_protocol.md
   model-executor:
   - vllm_omni/attention/
   - vllm_omni/experimental/
@@ -74,11 +75,15 @@ path_owners:
   - tests/
   tooling:
   - tools/
+  - apps/ComfyUI-vLLM-Omni/
   runtime-core:
   - vllm_omni/__init__.py
   - vllm_omni/data_entry_keys.py
+  - vllm_omni/patch.py
   - vllm_omni/request.py
 
+  host-weight-runtime:
+  - vllm_omni/host_weight_runtime/
 # Direct review destination for every structural owner above. The audit checks
 # that each route has a real current knowledge entrypoint.
 owner_documents:
@@ -91,7 +96,7 @@ owner_documents:
   diffusion:
   - knowledge/repos/vllm-omni/components/diffusion/rules.md
   distributed:
-  - knowledge/repos/vllm-omni/components/distributed/_index.md
+  - knowledge/repos/vllm-omni/components/distributed/rules.md
   documentation:
   - knowledge/general/docs/_index.md
   model-executor:
@@ -105,17 +110,23 @@ owner_documents:
   testing:
   - knowledge/repos/vllm-omni/ci/_index.md
   tooling:
-  - knowledge/repos/vllm-omni/rules.md
+  - knowledge/repos/vllm-omni/tooling/rules.md
   runtime-core:
   - knowledge/repos/vllm-omni/components/model-executor/rules.md
 
+  host-weight-runtime:
+  - knowledge/repos/vllm-omni/components/host-weight-runtime/rules.md
 ignored_paths:
 - pattern: .gitignore
   reason: repository metadata
+- pattern: .markdownlint.yaml
+  reason: repository tooling（PR #6273 引入 markdownlint）
 - pattern: .pre-commit-config.yaml
   reason: repository tooling
 - pattern: .readthedocs.yaml
   reason: documentation tooling
+- pattern: .readthedocs.yml
+  reason: documentation tooling（上游在 PR #6129 改了扩展名）
 - pattern: CODE_OF_CONDUCT.md
   reason: community metadata
 - pattern: CONTRIBUTING.md

diff --git a/doc/architecture/KNOWLEDGE.md b/doc/architecture/KNOWLEDGE.md
@@ -42,7 +42,7 @@ extensions merely because they are absent from the common source.
   history was removed — used for page frontmatter).
 - **Code-mirror pin:** the `knowledge/repos/vllm-omni/components/` source maps
   are verified against vllm-omni `main @
-  807db6efd70ff2e9b55a63d6e1b0530e2b74f8f2`. The canonical machine baseline
+1e74807c356be5cba4239faae7c38763fe1a44be`. The canonical machine baseline
   is `adapters/vllm_omni/release_baseline.yaml`.
 - **AFD code-mirror pin:** the `knowledge/repos/afd-plugin/components/` owner
   maps and architecture summaries are verified against

diff --git a/knowledge/general/ci/guides/inspect-existing-tests-first.md b/knowledge/general/ci/guides/inspect-existing-tests-first.md
@@ -4,7 +4,7 @@ created: 2026-07-10
 updated: 2026-07-16
 type: guide
 tags: [general, ci]
-sources: ["#3297", "tests/e2e/accuracy/test_gebench_h100_smoke.py", "tests/e2e/accuracy/test_hunyuan_image3.py"]
+sources: ["#3297", "tests/e2e/accuracy/test_hunyuan_image3.py", "tests/e2e/accuracy/conftest.py"]
 ---
 
 # 规则：先看现有代码，再谈方案
@@ -16,13 +16,11 @@ sources: ["#3297", "tests/e2e/accuracy/test_gebench_h100_smoke.py", "tests/e2e/a
 - 讨论"用 CLIP-score 替代"、"改 GenBench 砍 it2i"、"采集 9 小时 baseline"
 - 写了 300 行方案对比文档
 
-结果用户直接去看仓库：
-```
-tests/e2e/accuracy/test_gebench_h100_smoke.py
-```
-**已经存在**，跑的就是 type3/type4 T2I，用 `/v1/images/generations`，judge 是 VLM-as-judge（Qwen2.5-VL-7B-Instruct），**零 mmdet/mmcv 依赖**。
-
-`--gebench-model` 还是 CLI 参数。加一行 `--gebench-model Tencent/HunyuanImage-3.0-Instruct` 就能跑。
+结果用户直接去看当前 target 的 `tests/e2e/accuracy/`：旧记录中的
+`test_gebench_h100_smoke.py` 和 `test_gedit_bench_h100_smoke.py` 已经删除；当前
+HunyuanImage3 的入口是 `tests/e2e/accuracy/test_hunyuan_image3.py`，并由
+`tests/e2e/accuracy/conftest.py` 提供仍然存在的 accuracy fixtures。旧的
+`--gebench-model` 路径不能再当作现行合同。
 
 我前面所有工作（踩 mmcv 坑、建 Py3.10 venv、写 GenEval 集成代码）全部白做。
 
@@ -45,23 +43,23 @@ tests/e2e/accuracy/test_gebench_h100_smoke.py
 | 目录 | 内容 |
 |---|---|
 | `tests/e2e/accuracy/` | 所有精度 CI 入口 |
-| `tests/e2e/accuracy/conftest.py` | fixture 和 CLI option（`--gebench-model`, `--gedit-model`, `--accuracy-judge-model` 等） |
-| `tests/e2e/accuracy/test_gebench_h100_smoke.py` | T2I 精度（type3/type4）用 VLM judge |
-| `tests/e2e/accuracy/test_gedit_bench_h100_smoke.py` | IT2I 精度，同款 judge 路径 |
+| `tests/e2e/accuracy/conftest.py` | 当前仍存在的 Wan2.2/HunyuanVideo accuracy fixtures 和 CLI options |
+| `tests/e2e/accuracy/test_hunyuan_image3.py` | HunyuanImage3 IT2I/COT 对齐入口 |
+| `tests/e2e/accuracy/test_hunyuan_image3_pixel_accuracy.py` | HunyuanImage3 像素精度入口 |
 | `tests/e2e/accuracy/helpers.py` | `reset_artifact_dir` 等 |
-| `vllm_omni/benchmarks/accuracy/text_to_image/gbench.py` | GEBench 实现（type3/type4 走 `/v1/images/generations`，type1/2/5 走 `/v1/images/edits`） |
 
 ## 下一次做新模型精度 CI
 
-抄 `test_gebench_h100_smoke.py`，改 `--gebench-model` 参数。完成。
-**除非有强理由**（比如新模型 T2I endpoint 不同、判据不同），否则不要考虑 GenEval / CLIP-score / 自研评分器。
+先从当前 `tests/e2e/accuracy/` 选择语义最接近的幸存者，读取它的 fixture、CLI
+选项和运行方式，再决定复用还是新增；不要假设历史 GEBench 文件或参数仍存在。
 
 ## 判据模板
 
 用户问"做 XX 精度 CI"时，先回答 3 个问题再提方案：
 1. 团队现有类似测试文件？叫什么名字？
 2. 它的 fixture 和 CLI option 我的模型能复用吗？
-3. 跑一下 `pytest --gebench-model <my-model>` 会发生什么？报错才说明需要改，没报错就结束了
+3. 跑一下当前幸存者的最小 pytest 入口会发生什么？只有现行路径的采集或运行错误
+   才说明需要改，不要为已删除的 slug 重建测试文件。
 
 ## HunyuanImage3 现成 IT2I accuracy pytest（2026-06-02）
 

diff --git a/knowledge/general/review/guides/review-execution-contract.md b/knowledge/general/review/guides/review-execution-contract.md
@@ -1,10 +1,10 @@
 ---
 title: "独立审查执行合同"
 created: 2026-07-13
-updated: 2026-07-31
+updated: 2026-09-02
 type: guide
 tags: [general, review]
-sources: ["InferMatrixCopilot Issue #17", "InferMatrixCopilot Issue #24", "zuiho-kai/claude-workflow-starter@c217fc6"]
+sources: ["InferMatrixCopilot Issue #17", "InferMatrixCopilot Issue #24", "vllm-project/vllm-omni PR #5871", "zuiho-kai/claude-workflow-starter@c217fc6"]
 ---
 
 # 独立审查执行合同
@@ -46,6 +46,12 @@ sources: ["InferMatrixCopilot Issue #17", "InferMatrixCopilot Issue #24", "zuiho
 
 CI 默认只作为状态证据；只有首个失败异常与 frozen diff 重叠或阻塞判决时才打开日志。纯文档改动跳过依赖预检和 pytest，只做 diff hygiene、链接/构建检查以及对被引用 live contract 的有界核对。
 
+远端 head 必须物化为隔离快照或只用 SHA-addressed read；detached worktree 只冻结身份，不是
+安全边界。fork/untrusted head 的 import、测试、build、hook 和 repo-configurable tool 只有在
+无 secret、限制文件系统/网络/资源且用后销毁的 sandbox 中才可执行，否则只做静态读取与已有 CI。
+快照指纹必须覆盖 tracked、index、任务内 untracked 与 ignored bytes，并在每组可能改写文件的验证
+前后及交付前复核；只断言 `HEAD` 或只记录 untracked 文件名不足以证明证据未漂移。^[vLLM-Omni PR #5871]
+
 验证记录必须包含 `{repo, head_sha, command, result, environment_fingerprint}`。环境指纹至少覆盖依赖锁摘要、Python 和平台；只有依赖指纹匹配才复用环境。head 变化使旧测试结果失效，但依赖没有变化时不重建环境。预检失败就报告具体不兼容项，不继续运行或声称 pytest 已验证。预检通过后，目标测试和静态检查应与源码审查并行，不能等模型审完才启动。每条变化语义已有 finding 或明确 no-issue 结论后停止，不为增加信心继续追加搜索。
 
 ## 完成条件

diff --git a/knowledge/repos/vllm-omni/_index.md b/knowledge/repos/vllm-omni/_index.md
@@ -1,7 +1,7 @@
 ---
 title: "vLLM-Omni 入口"
 created: 2026-07-10
-updated: 2026-08-23
+updated: 2026-09-02
 type: index
 tags: [vllm-omni]
 sources: []
@@ -42,5 +42,6 @@ owner 仍不明确时才看 [components 职责表](components/_index.md)；模
 | bug 和行为异常 | [debug](debug/_index.md) |
 | Git、PR、rebase | [git](git/_index.md)、[upstream rebase](rebase/_index.md) |
 | benchmark / profiling | [benchmark](benchmark/_index.md) |
+| ComfyUI、示例 app 和客户端适配 | [tooling](tooling/_index.md) |
 | 远端验证 | [remote](remote/_index.md) |
 | 关键模型与负责人 | [owners](owners/_index.md) |
diff --git a/knowledge/repos/vllm-omni/benchmark/_index.md b/knowledge/repos/vllm-omni/benchmark/_index.md
@@ -1,10 +1,10 @@
 ---
 title: "vLLM-Omni 性能与 Profiling"
 created: 2026-07-10
-updated: 2026-07-10
+updated: 2026-09-05
 type: index
 tags: [vllm-omni, benchmark]
-sources: []
+sources: [benchmarks/tts/bench_tts.py, benchmarks/tts/model_configs.yaml, "PR #6522", "PR #6634", "PR #6818", vllm_omni/benchmarks/data_modules/omniinteract_dataset.py, vllm_omni/benchmarks/omniinteract.py, vllm_omni/benchmarks/patch/patch.py, tests/benchmarks/patch/test_patch.py, vllm_omni/benchmarks/duplex/, vllm_omni/entrypoints/cli/benchmark/omni_duplex_eval.py, vllm_omni/experimental/fullduplex/client.py]
 ---
 
 # vLLM-Omni 性能与 Profiling
@@ -21,7 +21,13 @@ sources: []
 
 | 遇到什么 | 查看哪里 |
 |---|---|
+| 新增/审查 perf JSON、warmup 覆盖、realtime artifact 或 Hub dataset fallback | [benchmark rules](rules.md) |
 | 查看旧 benchmark 总览 | [overview](overview.md) |
-| 运行 AR graph 或 Hunyuan benchmark | [benchmark guides](guides/_index.md) |
+| 运行 AR graph、Hunyuan 或 MiniCPM-o Omni-DuplexEval benchmark | [benchmark guides](guides/_index.md) |
 | 调查 profiling、模型加载和性能验证错误 | [benchmark incidents](incidents/_index.md) |
 | 查询历史结果 | [results](results/_index.md) |
+| 运行/审查 OmniInteract native-duplex serving benchmark（client ITL 优先，Stage-0 仅为无正 client ITL 的受限恢复） | [OmniInteract realtime guide](guides/omniinteract-realtime.md) |
+
+`benchmarks/tts/model_configs.yaml` 是共享 TTS runner registry；新模型在这里声明 model、deploy、voice/
+reference 与 workload，结果保留解析配置、seed、speed、并发和音频属性。IndexTTS 2.5 条目只证明
+harness 可路由；没有 native 2.5 baseline 时不得声称性能等价。^[PR #5957]
diff --git a/knowledge/repos/vllm-omni/benchmark/guides/_index.md b/knowledge/repos/vllm-omni/benchmark/guides/_index.md
@@ -1,10 +1,10 @@
 ---
 title: "vLLM-Omni 性能指南"
 created: 2026-07-10
-updated: 2026-07-10
+updated: 2026-09-04
 type: index
 tags: [vllm-omni, benchmark]
-sources: []
+sources: ["PR #6522", "PR #6634", vllm_omni/benchmarks/data_modules/omniinteract_dataset.py, vllm_omni/benchmarks/omniinteract.py, vllm_omni/benchmarks/duplex/]
 ---
 
 # vLLM-Omni 性能指南
@@ -23,3 +23,5 @@ sources: []
 | 验证动态或连续 batching | [dynamic batching](dynamic-batching-validation.md) |
 | 验证分叉执行路径 | [divergent path](divergent-path-validation.md) |
 | 查看旧 plan/validation 总入口 | [plan and validation](plan-and-validation.md) |
+| 复现或审查 OmniInteract realtime serving runner | [OmniInteract realtime](omniinteract-realtime.md) |
+| 生成、评分或审查 MiniCPM-o Omni-DuplexEval artifact | [Omni-DuplexEval](omni-duplex-eval.md) |
diff --git a/knowledge/repos/vllm-omni/benchmark/guides/benchmark-scope.md b/knowledge/repos/vllm-omni/benchmark/guides/benchmark-scope.md
@@ -4,7 +4,7 @@ created: 2026-07-10
 updated: 2026-07-16
 type: guide
 tags: [vllm-omni, benchmark]
-sources: ["#3767", "#3938"]
+sources: ["#3767", "#3938", "PR #5957", benchmarks/tts/bench_tts.py, benchmarks/tts/model_configs.yaml]
 ---
 
 # vLLM-Omni Benchmark 口径
@@ -166,3 +166,14 @@ candidate PR 只能来自三种来源：
 - 禁止把第二种结果简称成 “AR 极限”。
 
 **一句话规则**：benchmark PR 是尺子，不是自动成为被测对象；candidate PR 是用户需求，不是 agent 推断。先锁四元组，再启动任何远端长跑。
+
+## Shared TTS runner 必须分离 registry identity 和实际 served model
+
+- `--model` 只选择 `model_configs.yaml` 的 workload/deploy/voice 配置；服务从本地 bundle
+  启动时，`--served-model-name` 独立指定发给 `vllm bench serve` 的 model 值，不得
+  因此变更 registry key 或工作负载。
+- 为请求注入 seed 前必须 copy task `extra_body`，不能在多轮 sweep 中污染共享
+  registry dict；`--num-warmups` 必须非负；`argparse.REMAINDER` 交给底层 CLI 前只移除
+  首个 literal `--`，其余参数和顺序原样保留。
+- 验收：用 local served name + registry key、连续两轮不同 seed、负 warmup 和带/不带
+  separator 的 remainder 构造最终 argv；registry 输入在调用后保持不变。^[PR #5957]