[dougbtv]

Summary

• add the v0.30.0 carry record for the realtime implementation in [carry] Replace temorary turn-based /v1/realtime implementation with upstreamed version #59
• link the carry to INFERENG-11446
• record the exact ordered five-commit replay from current main to ncao/upstream-realtime
• link all five upstream PRs, which are merged but absent from the selected v0.30.0 release
• keep mutable ownership, approval, lifecycle, and Midstream PR links in Jira

This PR contains carry metadata only. It targets ncao/upstream-realtime and does not change Nick's realtime implementation or tests.

Replay evidence

The recorded commits form one contiguous series:

1. e167550d — upstream [Frontend] OpenAI-compliant fullduplex /v1/realtime with Qwen3-Omni support vllm-project/vllm-omni#7285
2. 255c0ed4 — upstream [Bugfix] Fix Qwen3-Omni realtime routing with typed stage configs vllm-project/vllm-omni#8279
3. 68b72d08 — upstream [Core] Generalized turn-based /v1/realtime implementation vllm-project/vllm-omni#8339
4. fac146be — upstream [BugFix] Optimize turn-based /v1/realtime auto truncation vllm-project/vllm-omni#8566
5. 3598c550 — upstream [Tests] Fix Qwen3-Omni E2E LiveKit Test vllm-project/vllm-omni#8294

The first commit's parent is current main at 7b634ebb; the final commit is the current ncao/upstream-realtime head.

Validation

• pre-commit passed for midstream/carries/v0.30.0/INFERENG-11446.yml
• YAML schema, Jira/file identity, upstream-tag directory, and one-line description validated
• every recorded commit object resolves
• the five commits are a contiguous ordered series from 7b634ebb to 3598c550
• git diff --check

The Jira remains omni-carry-proposed; this metadata PR does not itself approve the carry for merge or replay.

CI note

The Ent trigger succeeded. Downstream nm-cicd run 37976669403 stopped during input resolution because v0.30.0 has no entry in midstream/vllm-wheels.yml; no wheel, image, or test job ran. This is the same pre-existing release-input gap seen on the policy and dogfood PRs and is unrelated to this YAML-only change.

Worked on by

• Doug Smith