From 8081ef3512950d6e707465e48a95ad3090f596a6 Mon Sep 17 00:00:00 2001
From: mattmillerai <7741082+mattmillerai@users.noreply.github.com>
Date: Mon, 14 Sep 2026 06:47:05 +0000
Subject: [PATCH] chore: sync vendored Comfy Router spec from cloud@4dc6e93

---
 spec/router-openapi.yaml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/spec/router-openapi.yaml b/spec/router-openapi.yaml
index 9776645..7c06afa 100644
--- a/spec/router-openapi.yaml
+++ b/spec/router-openapi.yaml
@@ -346,7 +346,7 @@ components:
       additionalProperties: true
     RouterModelSegment:
       type: string
-      description: Lowercase `model` segment of the canonical `{provider}/{model}[/{variant}]` model ID - the model to run within that provider. Shared by the invocation route's `model` path parameter and a catalog entry's `model` field, for the same no-drift reason as `RouterProviderSegment`.
+      description: Lowercase `model` segment of the canonical `{provider}/{model}` model ID - the model to run within that provider. Shared by the invocation route's `model` path parameter and a catalog entry's `model` field, for the same no-drift reason as `RouterProviderSegment`.
       pattern: ^[a-z0-9]+([._-][a-z0-9]+)*$
       maxLength: 128
       example: flux-2-pro
@@ -359,7 +359,7 @@ components:
       example: q7Fm2xTn9pLd4RsV
     RouterProviderSegment:
       type: string
-      description: Lowercase `provider` segment of the canonical `{provider}/{model}[/{variant}]` model ID - the partner whose model is being addressed. The invocation route's `provider` path parameter and a catalog entry's `provider` field both reference this one schema, which is what keeps the listed IDs and the accepted IDs from drifting apart.
+      description: Lowercase `provider` segment of the canonical `{provider}/{model}` model ID - the partner whose model is being addressed. The invocation route's `provider` path parameter and a catalog entry's `provider` field both reference this one schema, which is what keeps the listed IDs and the accepted IDs from drifting apart.
       pattern: ^[a-z0-9]+([._-][a-z0-9]+)*$
       maxLength: 64
       example: bfl
@@ -518,14 +518,14 @@ components:
       name: model
       in: path
       required: true
-      description: Lowercase model segment of the canonical `{provider}/{model}[/{variant}]` model ID - the model to run within that provider.
+      description: Lowercase model segment of the canonical `{provider}/{model}` model ID - the model to run within that provider.
       schema:
         $ref: '#/components/schemas/RouterModelSegment'
     RouterProvider:
       name: provider
       in: path
       required: true
-      description: Lowercase provider segment of the canonical `{provider}/{model}[/{variant}]` model ID - the partner whose model is being run.
+      description: Lowercase provider segment of the canonical `{provider}/{model}` model ID - the partner whose model is being run.
       schema:
         $ref: '#/components/schemas/RouterProviderSegment'
   headers: