ComfyUI as an engine of the cluster's own

A model whose profiles run engine comfyui is placed on a node's card like
any other, and makes pictures there. ComfyUI asks for no key, so the agent
starts it behind llmgw comfyui-gate: ComfyUI on the loopback, the gate on
the replica's port demanding the replica's key and letting through only
what the router asks — queueing, waiting, fetching, cancelling. The gate
answers the agent's /health and /v1/models, shows ComfyUI the fetched
weights by their own names, and gives each replica its own base directory.
ComfyUI runs as the gate's child, so its card memory is the replica's.

A node offers the engine when agent.yaml names its ComfyUI
(engines.comfyui.dir). The model's comfyui: block names the workflow and,
for a source that is a set of files, the checkpoint.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/admin-api.openapi.json

@@ -8576,6 +8576,20 @@
           }
         }
       },
+      "catalog.ComfyUI": {
+        "type": "object",
+        "description": "ComfyUI is a ComfyUI model's workflow and checkpoint.",
+        "properties": {
+          "workflow": {
+            "type": "string",
+            "description": "Workflow is a built-in's name (flux-schnell, the default, or flux-dev) or a JSON file on the control plane, in ComfyUI's API format."
+          },
+          "checkpoint": {
+            "type": "string",
+            "description": "Checkpoint is the file the workflow's {{checkpoint}} names: the source's own name unless set, which a source that is a set of files must."
+          }
+        }
+      },
       "catalog.EvalGate": {
         "type": "object",
         "description": "EvalGate is a quality suite a model's new weights must pass.",
@@ -8683,6 +8697,10 @@
             "$ref": "#/components/schemas/catalog.External",
             "description": "External is a model served by someone else — an OpenAI-compatible API outside the cluster — rather than by replicas placed here. Such a model has no profiles and nothing is placed for it; the router sends its requests to the provider. Most useful named in another model's fallbacks: used only when the cluster has no capacity left. Its prompts leave the cluster, so which keys may name it is worth an allowlist."
           },
+          "comfyui": {
+            "$ref": "#/components/schemas/catalog.ComfyUI",
+            "description": "ComfyUI is how a model whose profiles run engine comfyui makes its pictures: the workflow, and the file it loads."
+          },
           "adapters": {
             "type": "array",
             "items": {