qwen3.6-windows-server v1.3.7 — portable Windows launcher

qwen3.6-windows-server v1.3.7

Blackwell-only cleanup release. The two AutoRound INT4 snapshots for the
RTX 5090 are gone; NVFP4 is now the sole 5090 path. Ampere/Ada
(3090/4090) are unaffected, AutoRound stays the recommended quant
there.

What changed

• Removed snapshots: rtx5090 (240k ctx, MTP n=6, AutoRound INT4)
  and rtx5090_max (280k ctx, MTP n=3, AutoRound INT4). The matching
  snapshots/start_5090.{py,bat} and snapshots/start_5090_max.{py,bat}
  files are deleted.
• Reason: on Blackwell sm_120 the AutoRound (Marlin INT4) FFN GEMMs
  hit the ~170W prefill ceiling documented in
  docs/SM120_GDN_CEILING.md, capping
  prefill at ~1.1k tok/s. The NVFP4 path routes FFN/QKV/proj through
  FlashInfer's native sm_120 fp4_gemm tensor cores and runs at full
  TDP: ~5,300-7,460 tok/s prefill, ~92 tok/s decode. The AutoRound
  configs booted and ran on the 5090, but the prefill cap made them too
  slow to keep shipping as user-facing options.
• 5090 dashboard now exposes two cards: rtx5090_nvfp4 (200k ctx,
  MTP n=6, default) and rtx5090_nvfp4_vision (180k ctx, experimental,
  image/video input). Both use the Peutlefaire NVFP4 weights.
• Compatibility matrix updated: Blackwell sm_120 + Marlin AutoRound INT4 is now flagged warn with a note about the prefill ceiling.
  Added a separate Blackwell sm_120 + NVFP4 row marked ok.
• Docs swept: README and 16 docs under docs/ updated so every
  forward-looking 5090 recommendation points at NVFP4. Historical
  AutoRound bench numbers retained in BLACKWELL.md, HARDWARE.md, and
  TUNING.md as reference, labeled "removed in v1.3.7" or "historical".
• Boot-time clarification added to TROUBLESHOOTING.md, BLACKWELL.md,
  and the rtx5090_nvfp4 notes: the FlashInfer fp4_gemm "Tuning"
  progress bars appear on every boot. First-ever boot takes ~9 min
  (JIT-compiles kernels + autotunes tactics). Every subsequent boot
  finishes in ~1-2 min because the compiled kernel binaries are cached
  under ~/.cache/flashinfer/, only the tactic selection re-runs. This
  is expected, not a regression.

Who is affected

• 5090 users: if you had been booting rtx5090 or rtx5090_max,
  those cards are gone. Use rtx5090_nvfp4 (or _vision) instead.
  You will need the Peutlefaire NVFP4 weights on disk; set
  VLLM_NVFP4_MODEL_DIR if they're not at the default location
  (models/Qwen3.6-27B-NVFP4). See
  docs/MODELS.md for the download path.
• 3090 / 4090 users: no behaviour change. AutoRound stays the
  recommended quant on Ampere/Ada. Wheel is unchanged
  (vllm-0.19.0+devnen.3).
• Wheels: Ampere stays on vllm-0.19.0+devnen.3, Blackwell stays
  on vllm-0.20.0+cu132.devnen.2. Inference behaviour for surviving
  snapshots is identical to v1.3.6.

Upgrading

update.bat

The launcher zip is replaced; venv\, models\, logs\,
cuda13_shim\ and user_config.json are preserved. The runtime
install is not rerun because the bundled wheel did not change. If you
created a custom snapshot named start_5090.py or start_5090_max.py,
keep your local copy: the launcher reads any start_*.py in
snapshots/, the deletion only removes the in-zip files.

Verification

After upgrading, the Blackwell zip's dashboard should show only two
5090 cards: rtx5090_nvfp4 and rtx5090_nvfp4_vision. Launching
rtx5090_nvfp4 should boot in ~1-2 min on a host that has booted NVFP4
before (kernel binaries cached), ~9 min the first time. After
Application startup complete, python windows_tools\bench.py should
report ~92 tok/s steady decode at ~580W.

Files

• qwen3.6-windows-server-portable-x64-ampere.zip (and the unsuffixed
  alias for legacy in-place updates from pre-v1.2.3 installs)
• qwen3.6-windows-server-portable-x64-blackwell.zip
• SHA256SUMS.txt