Rename Step 3.5 Flash recipe to its stepfun-ai/Step-3.5-Flash hub path

Key the checkpoint by its canonical Hugging Face repo id
(https://huggingface.co/stepfun-ai/Step-3.5-Flash): rename the org folder
step3p5 -> stepfun-ai and the model folder Step3.5-Flash -> Step-3.5-Flash so
the on-disk path mirrors the model-hub path exactly, per the
models/<org>/<model_id> convention.

Update the recipe-path references in docs/source/guides/10_recipes.rst,
modelopt_recipes/ptq.md, the unreleased 0.47 CHANGELOG entry, and the
recipe-docs test docstring. Released CHANGELOG entries keep their historical
paths. The Step3p5* architecture class names (trust_remote_code modeling code)
are unaffected.

Signed-off-by: Shengliang Xu <shengliangx@nvidia.com>

Author: shengliangxu

CHANGELOG.rst

@@ -24,7 +24,7 @@ Changelog
 
 **Backward Breaking Changes**
 
-- Move the checkpoint-mirror recipe tier from ``huggingface/models/<org>/<checkpoint>/`` to the top-level ``models/<org>/<checkpoint>/`` (and the Step 3.5 Flash recipe from ``huggingface/step3p5/Step3.5-Flash/ptq/`` to ``models/step3p5/Step3.5-Flash/ptq/``), so instance-specific recipes sit beside ``general/`` and ``huggingface/`` instead of under the per-``model_type`` tree. Drop the ``huggingface/`` prefix in any saved ``--recipe`` paths.
+- Move the checkpoint-mirror recipe tier from ``huggingface/models/<org>/<checkpoint>/`` to the top-level ``models/<org>/<checkpoint>/`` (and the Step 3.5 Flash recipe from ``huggingface/step3p5/Step3.5-Flash/ptq/`` to ``models/stepfun-ai/Step-3.5-Flash/ptq/``), so instance-specific recipes sit beside ``general/`` and ``huggingface/`` instead of under the per-``model_type`` tree. Drop the ``huggingface/`` prefix in any saved ``--recipe`` paths.
 - Move the Mistral Medium 3.5 checkpoint-mirror recipe from ``models/nvidia/Mistral-Medium-3.5-128B-NVFP4/ptq/nvfp4-max-calib`` to ``models/mistralai/Mistral-Medium-3.5-128B/ptq/nvfp4-max-calib``, keying it by the canonical Hugging Face base model. Update any saved ``--recipe`` paths to the new location.
 - Remove the ``--auto_quantize_bits``, ``--auto_quantize_method``, ``--auto_quantize_score_size``, ``--auto_quantize_cost_model`` and ``--auto_quantize_active_moe_expert_ratio`` flags from ``examples/hf_ptq`` (deprecated in 0.46). Use an AutoQuantize ``--recipe`` from ``modelopt_recipes/general/auto_quantize/`` instead. Those recipes now also splice in the shared base ``cost_excluded_layers`` unit, which the removed CLI applied unconditionally, so a VL model keeps its vision tower and MTP layers out of the effective-bits denominator. On a VL model this changes the per-layer cost weights, so an existing ``--auto_quantize_checkpoint`` from an earlier release is rejected with "Use a different checkpoint path"; delete or repoint it to re-run the search.
 - Remove the ``examples/llm_ptq`` symlink and the ``examples/vlm_ptq`` forwarder (both deprecated in 0.46). Use ``examples/hf_ptq``, passing ``--vlm`` for vision-language models.

docs/source/guides/10_recipes.rst

@@ -534,7 +534,7 @@ for the layout conventions and recipe-lookup order.
 
    * - Recipe path
      - Description
-   * - ``models/step3p5/Step3.5-Flash/ptq/nvfp4-mlp-only``
+   * - ``models/stepfun-ai/Step-3.5-Flash/ptq/nvfp4-mlp-only``
      - NVFP4 MLP-only for Step 3.5 Flash MoE model
    * - ``huggingface/minimax_m3_vl/ptq/mxfp8_nvfp4_experts``
      - MXFP8 language-model base with MSE-calibrated NVFP4 routed experts for MiniMax-M3

…p5/Step3.5-Flash/ptq/nvfp4-mlp-only.yaml …i/Step-3.5-Flash/ptq/nvfp4-mlp-only.yamlmodelopt_recipes/models/step3p5/Step3.5-Flash/ptq/nvfp4-mlp-only.yaml renamed to modelopt_recipes/models/stepfun-ai/Step-3.5-Flash/ptq/nvfp4-mlp-only.yaml modelopt_recipes/models/step3p5/Step3.5-Flash/ptq/nvfp4-mlp-only.yaml renamed to modelopt_recipes/models/stepfun-ai/Step-3.5-Flash/ptq/nvfp4-mlp-only.yaml

@@ -296,7 +296,7 @@ general recipes never enable output quantizers, and the pattern must stay scoped
 to GEMM outputs — a `DynamicQuantize` on non-GEMM outputs (embedding lookup,
 pooling) fails to compile in TensorRT.
 
-A lighter case: **`models/step3p5/Step3.5-Flash/ptq/nvfp4-mlp-only`** is close to
+A lighter case: **`models/stepfun-ai/Step-3.5-Flash/ptq/nvfp4-mlp-only`** is close to
 `general/ptq/nvfp4_mlp_only` (NVFP4 on MoE/MLP weights+inputs, FP8 KV) but pinned
 to one released checkpoint and carrying instance-specific disables
 (`share_expert`, `moe.gate`, the conv1d branches).

modelopt_recipes/ptq.md

@@ -88,9 +88,8 @@ def test_every_model_specific_ptq_dir_is_mentioned():
     """Every model dir under huggingface/ or models/ with PTQ recipes must appear in ptq.md.
 
     The identifier checked is the directory containing the ptq/ folder — the
-    HF model_type (e.g. ``gemma4``), a nested checkpoint dir (e.g.
-    ``Step3.5-Flash``), or a models/<org>/<checkpoint> leaf (e.g.
-    ``Nemotron-3-Nano-4B``).
+    HF ``model_type`` (e.g. ``gemma4``) or a models/<org>/<model_id> leaf
+    (e.g. ``Step-3.5-Flash``, ``Nemotron-3-Nano-4B-BF16``).
     """
     doc = _ptq_md_text()
     search_dirs = (RECIPES_DIR / "huggingface", RECIPES_DIR / "models")