vLLM-MetaX Upgrade

Read and apply the complete shared upgrade workflow before this coordinator workflow. It owns environment confirmation, trust boundaries, upstream-first adaptation, validation and durable progress.

Own the whole requested support matrix, dependency graph, domain assignments and acceptance obligations. These roles may run sequentially; parallel agents are optional.

Plan the full upgrade

Use the existing run in full mode. After the common gate passes, define the agreed model/configuration matrix and evidence obligations, and persist its machine-readable rows before claiming support. Supported rows record their exact configuration, linked tasks and acceptance kinds; unsupported rows give the rejection reason. Create disposition tasks covering every baseline production/build/requirements inventory entry, including startup and build infrastructure outside the four specialist domains.

Read orchestration.md when constructing or expanding the graph. Build typed import, startup, side-effect, call, data and conditional edges. Plan around changed contracts and reachable dependencies; collapse strongly connected components into coordinated adaptation units rather than requiring cyclic members to import successfully before source adaptation.

Dispatch and schedule

• Assign model, attention, registry and patch units to their corresponding skills. Their standalone scope boundaries permit coordinated dispatch here; shared rules remain in common and do not need to be copied into each assignment.
• Cover platform selection, distributed communication, workers, allocator/cache, foundational ops, build/extension ABI and entry points through explicit contract review when no specialist exists.
• Keep one owner per shared unit and one authoritative run. Workers return newly discovered edges, contract changes, dispositions and evidence to the coordinator.
• When a prerequisite becomes ready, schedule its blocked consumer obligations. Prioritize an early minimal normal-entry vertical path, then expand to the agreed model, dtype/quantization, phase, parallel, MTP, graph and optional-feature matrix.

Full completion and handoff

Check every supported matrix row for actual production reachability and current acceptance evidence. Full completion requires a disposition for every baseline production/build/requirements file and a required passing normal-entry e2e obligation for every supported matrix row, together with each row's other declared evidence kinds. At least one row must be supported. Required blocked obligations keep the run incomplete; deliberately unsupported rows need their intended capability rejection, not a claimed pass.

At handoff, relate the remaining units and blocked closures to the support matrix and the common workflow's persisted next actions. Do not substitute a completed component or a narrower test result for the full-upgrade acceptance obligations.