feat: add option to preserve class ordering during model deployment

Add DISABLE_CLASS_SORTING configuration option to prevent automatic
alphabetical sorting of class names during YOLO model deployment.
Users can set ROBOFLOW_DISABLE_CLASS_SORTING=true to maintain custom
class ordering from model checkpoints.

- Add DISABLE_CLASS_SORTING to config.py (defaults to false)
- Update model_processor.py to conditionally apply sorting
- Include warning comment about user responsibility for proper class ordering
- Maintain backwards compatibility with default behavior

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: davidnichols-ops

roboflow/config.py

@@ -86,6 +86,7 @@ def get_conditional_configuration_variable(key, default):
 
 RF_WORKSPACES = get_conditional_configuration_variable("workspaces", default={})
 TQDM_DISABLE = os.getenv("TQDM_DISABLE", None)
+DISABLE_CLASS_SORTING = os.getenv("ROBOFLOW_DISABLE_CLASS_SORTING", "false").lower() == "true"
 
 
 def load_roboflow_api_key(workspace_url=None):

roboflow/util/model_processor.py

@@ -7,6 +7,7 @@
 import yaml
 
 from roboflow.config import (
+    DISABLE_CLASS_SORTING,
     TASK_CLS,
     TASK_DET,
     TASK_OBB,
@@ -224,7 +225,11 @@ def _process_yolo(model_type: str, model_path: str, filename: str) -> tuple[str,
         class_names = []
         for i, val in enumerate(model_instance.names):
             class_names.append((val, model_instance.names[val]))
-        class_names.sort(key=lambda x: x[0])
+        # NOTE: When DISABLE_CLASS_SORTING is enabled, users are responsible for ensuring
+        # their model's names dict has properly ordered/sequential keys. Non-sequential keys
+        # may result in incorrect class-to-index mappings.
+        if not DISABLE_CLASS_SORTING:
+            class_names.sort(key=lambda x: x[0])
         class_names = [x[1] for x in class_names]
 
     if (