chore: sync vendored Comfy Router spec (cloud@f2cb906) - #108
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: Comment |
|
Superseded by #113 ( Every sync pull request on this branch prefix carries the FULL projected spec as of its own source commit, so the newer one contains everything this one did. Closing it automatically and deleting A superseded sync pull request that carries a commit other than the sync bot's is never closed automatically — this one carried none. |
Automated sync of the public Comfy Router spec,
projected from the canonical contract (internal notes stripped).
Source:
cloud@f2cb906.It lands at
spec/router-openapi.yamland is a contract of itsown — it is never merged into another vendored spec in this repo.
This PR is on its own per-source-commit branch (
chore/sync-router-spec-f2cb906); a laterspec change opens a separate PR and will not touch this branch, so a
regen commit pushed here is safe.
No Router operations are currently unserved (as of
cloud@f2cb906).This note auto-refreshes while this PR is open: a change to comfy-api's
exclude list rewrites this section in place, and a change to the
PUBLISHED Router surface opens its own sync PR carrying the set as of
ITS commit. Once this PR is merged the note is a permanent snapshot —
for the current state, check
services/comfy-api/drip/codegen.yamlinComfy-Org/cloud directly.
No code generation for this spec yet. Nothing in this repo
generates code from
spec/router-openapi.yaml, so this sync has no low layer toregenerate and the workflow that opened this pull request could not
prepare one for you.
That is not the same as nothing to do. This repo keeps a hand-written
surface coupled to this contract — the
error_typeclass table — witha drift check of its own, so a sync that adds an error bucket still
needs a commit here before this pull request goes green. When code
generation does land for this spec, its command is configured
upstream, in the same sync workflow that opened this PR, and this
section becomes the automatic one.