chore: sync vendored Comfy Router spec (cloud@9e788a8) - #105
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 #106 ( 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@9e788a8.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-9e788a8);a later spec 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@9e788a8).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 regeneration step for this spec yet. Nothing in this repo reads
spec/router-openapi.yaml, so there is no low layer to regenerate before merge andno spec-drift check to satisfy — merging vendors the contract and
nothing else. When Router code generation does land here, this
section should carry its command; it is configured upstream, in the
same sync workflow that opened this PR.