Fine-tune responses include qualified model registry names for models and checkpoints

Fine-tune retrieve and list-checkpoints responses now include qualified Together model registry names alongside object IDs. On GET /fine-tunes/{id}, use model_object_name and adapter_object_name (LoRA jobs) for the final artifacts in <project_slug>/<model_name> form. On GET /fine-tunes/{id}/checkpoints, each entry adds object_name with the same naming pattern (including -<step> or -adapter suffixes). Names are resolved on retrieve only, not on list jobs. If the project slug cannot be resolved, the name field falls back to the object ID.

On a completed job in the fine-tuning jobs dashboard, Output model shows the same qualified model_object_name and links to the registry model page.

See Model registry object IDs.