[ShuhaoZhangTony]

Add the real Host producer side for a separately qualified conditional PipelineMicrobatch + BidKV H4 tuple. Authenticate the original API→scheduler RID selection, preserve source-owned process/nonce/query bindings, and emit typed policy outcomes only after the original validation and builtin fallback decisions. Keep actual admitted/selected effects distinct from called/abstained/fallback outcomes; a missing condition or effect cannot become positive coverage.

This additive producer is paired with the Manager conditional registration/oracle/typed intake source release. It targets a new PP2TP1 tuple and does not reuse historical four-device qualification or change the current H3 runtime/source cohort. Historical plugin declarations do not admit Host0.31; new actual source, plugin declarations/wheels and independent tuple qualification are still required.

Companion Manager: vLLM-HUST/extension-manager#248 (depends on Manager PR247).

Validation: actual Host772 configuration stdin Ruff lint/format checks passed for these7 Python paths. All40 conditional behavior/negative scenarios plus3 typed-callable scenarios passed across recorded37+4+2 runs. Real private UDS/owned CPU child and loopback ephemeral HTTP deadline/socket shutdown tests passed; pidfd/proc exit and all socket/thread/UDS cleanup passed. Prior fixture/harness failures are retained. Actual Host producer execution, device work, repository CI, plugin adaptations/wheels and new tuple qualification remain unverified. No formal or performance result is claimed.

[ShuhaoZhangTony]

2026-11-08 maintainer disposition: closing this stale draft as an unmerged research experiment. It belongs to the October 18 H3/H4 stacked chain, has had no review or rebase activity, and does not provide model/device/current-main qualification. Its bounded CPU fixtures and negative evidence remain preserved in the branch/PR history, but none of them may be treated as an accepted runtime contract, compatibility result, or performance claim. Any still-needed behavior must be reintroduced as a small current-main PR with a standalone issue, supported source boundary, and end-to-end tests; do not revive the full stack.