Switch Qwen3.5 FP4 SGLang configs to nvidia/Qwen3.5-397B-A17B-NVFP4-V2

[hshrivastava-droid]

Updates the 4 Qwen3.5 FP4 SGLang agg configs (qwen3.5-fp4-b200-sglang ±mtp, qwen3.5-fp4-b300-sglang ±mtp) to the nvidia/Qwen3.5-397B-A17B-NVFP4-V2 checkpoint, pre-staged on the b200-dgxc and b300 clusters per the working-model-paths sheet.

• configs/nvidia-master.yaml: model: → V2 for the 4 SGLang keys
• launch_b200-dgxc.sh: qwen3.5-fp4 MODEL_PATH → /scratch/fsw/models/Qwen3.5-397B-A17B-NVFP4-V2 (per model-paths sheet for GCP B200 Lustre FS; same convention line 17 already uses for dsr1-fp4)
• launch_b300-nv.sh: V2 added to STAGED_MODELS so HF_HUB_CACHE_MOUNT resolves it to /scratch/models/Qwen3.5-397B-A17B-NVFP4-V2

b200-trt, b200-trt-mtp, and gb300-dynamo-sglang are intentionally left on V1 in this PR — they will migrate in follow-up PRs after their internal-fork sweeps confirm no V2 regression.

[github-actions]

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs

---

感谢你的贡献！请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md，然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人，你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板，包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have。

如需进行 PR 验证，请为此 PR 添加 full-sweep-fail-fast 标签（强烈推荐）— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled。

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动（flake），重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

[github-actions]

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs

---

感谢你的贡献！请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md，然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人，你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板，包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have。

如需进行 PR 验证，请为此 PR 添加 full-sweep-fail-fast 标签（强烈推荐）— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled。

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动（flake），重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

[claude]

LGTM — straightforward checkpoint swap.

Extended reasoning...

Overview

This PR swaps the checkpoint used for all 7 Qwen3.5 FP4 benchmark configs (b200 sglang/trt ±mtp, b300 sglang ±mtp, gb300 dynamo-sglang disagg) from nvidia/Qwen3.5-397B-A17B-NVFP4 to nvidia/Qwen3.5-397B-A17B-NVFP4-V2. Changes are confined to: the model: field for all 7 relevant keys in configs/nvidia-master.yaml, served-model-name in the 4 gb300 disagg recipe YAMLs, MODEL_PATH filename strings in launch_b200-dgxc.sh/launch_gb300-nv.sh, a new entry in the STAGED_MODELS array in launch_b300-nv.sh, and a matching perf-changelog.yaml entry.

Security risks

None — this is a benchmark config/recipe change with no code paths touching auth, secrets, or user input. The checkpoint name is a static string pointing to a pre-staged local path.

Level of scrutiny

Low. This is a mechanical, well-scoped model-checkpoint version bump following the exact pattern of prior similar PRs in this repo's history (e.g. recent H200 FP8 refresh, other model swaps). I cross-checked that all references to the old checkpoint name are updated consistently across the master config, the gb300/b300/b200 launcher scripts, and the recipe YAMLs, and that the aliasing scheme (served-model-name vs. model-path alias vs. STAGED_MODELS basename matching) stays internally consistent after the swap — no path or config was missed or left mismatched.

Other factors

No bugs were surfaced by the bug hunting system, and the two candidate issues it raised (missing Chinese translation, placeholder PR link) were checked and are non-issues — the changelog entry has a real PR link and translation isn't required for this template. No CODEOWNER-sensitive or business-logic code is touched.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29353750144
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=29353750144

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29370174289
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=29370174289

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29370502845
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=29370502845