Upstream sync 9/N: merge 0a1c5034f5 MiniMax M3 (conflict)

[roberteg16]

Context

Ninth step of the batched upstream catch-up. Stacked on #1101; chain is #1097 → #1098 → #1100 → #1101 → this. Retarget to gfx11 as the ones below land.

Conflict-only step: exactly one upstream commit.

Merged upstream commit	0a1c5034f5 "[Model] Add MiniMax M3 support (vllm-project#45381)"
Landed on upstream main	2026-06-15 17:01 UTC
Commits in this PR	1
Upstream size	108 files, +14746 / −323

A big commit that touches 12 files the fork has also modified, but only one actually conflicts.

Conflict and resolution

vllm/envs.py — both sides append new environment-variable declarations to the same block: the fork's ROCm switches (VLLM_MOE_AWQ_GEMV_HIP, VLLM_MOE_GPTQ_EXLLAMA, VLLM_MOE_HYBRID_W4A16, VLLM_MOE_HIP, VLLM_GDN_HIP, VLLM_ROCM_USE_MOE_WNA16_CUDA_KERNEL) and upstream's VLLM_MXFP8_EMULATION_DEQUANT_AT_LOAD. Purely additive — kept both.

Post-merge checks

Following the two silent breakages found earlier in this series (#1097, #1100), the standing checks were run rather than trusting the clean auto-merge:

• All seven declarations in that envs.py block still have a matching runtime entry in the environment_variables dict.
• Every ops.impl(...) registration in both torch_bindings.cpp files still resolves to a declared symbol — this commit touches csrc/libtorch_stable/ops.h, csrc/ops.h, torch_bindings.cpp and CMakeLists.txt, which is exactly the shape that broke in Upstream sync 5/N: merge 6635279d8a GGUF-to-plugin migration (conflict) #1097. Clean (the only hits were cuda_utils.h declarations and a code comment).

Test plan

• ROCm build + the four gfx1151 benchmarks — run on the stacked Upstream sync 10/N: merge f3858d5422 (21 commits, conflict-free) #1103, which contains this merge. All pass, no regression: decode within ±0.4%, TTFT within ±2.2%. Full table on Upstream sync 10/N: merge f3858d5422 (21 commits, conflict-free) #1103.