Schema-mirrored companion features

Summary#

When adding a new step to an existing workflow family, the safest path is to make it a strict counterpart of a proven sibling instead of inventing a new contract. Mirror the input/output shape, display semantics, and UI payloads so users can swap stages without adapters or relearning. Coordinate the frontend change as a paired deliverable, not an afterthought.

Problem#

New save/output capabilities often drift from adjacent preview/edit nodes in naming, socket shape, or emitted UI data, which creates workflow friction and frontend/backend mismatch.

Solution#

Reuse the existing node family's schema and naming, preserve the original artifact format when persisting, and emit the same UI-facing structure the neighboring stage already expects.

Failure Modes#

Socket names or payload shapes diverge from the sibling node
Save logic mutates format or drops metadata users expect to preserve
Backend support lands without the matching frontend wiring
Seeded or incoming state is not echoed back, so same-run UI behavior becomes inconsistent

Sources#

https://github.com/Comfy-Org/ComfyUI/pull/14701
https://github.com/Comfy-Org/ComfyUI/pull/14724
https://github.com/Comfy-Org/ComfyUI/pull/14102
https://github.com/Comfy-Org/ComfyUI/pull/14869
https://github.com/Comfy-Org/ComfyUI/pull/14867
https://github.com/Comfy-Org/ComfyUI/pull/14853
https://github.com/Comfy-Org/ComfyUI/pull/14424
https://github.com/Comfy-Org/ComfyUI/pull/14862
https://github.com/Comfy-Org/ComfyUI/pull/14643
https://github.com/GitHubDaily/GitHubDaily/pull/267
https://github.com/GitHubDaily/GitHubDaily/pull/52
https://github.com/fastapi/full-stack-fastapi-template/pull/2364
https://github.com/fastapi/full-stack-fastapi-template/pull/2333
https://github.com/fastapi/full-stack-fastapi-template/pull/2375
https://github.com/fastapi/full-stack-fastapi-template/pull/2361
https://github.com/fastapi/full-stack-fastapi-template/pull/2359
https://github.com/fastapi/full-stack-fastapi-template/pull/2368
https://github.com/fastapi/full-stack-fastapi-template/pull/2369
https://github.com/fastapi/full-stack-fastapi-template/pull/2343
https://github.com/fastapi/full-stack-fastapi-template/pull/2362
https://github.com/fastapi/full-stack-fastapi-template/pull/2367
https://github.com/fastapi/full-stack-fastapi-template/pull/2360
https://github.com/react/react/pull/36980
https://github.com/react/react/pull/36965
https://github.com/react/react/pull/36964
https://github.com/react/react/pull/36963
https://github.com/react/react/pull/36962
https://github.com/react/react/pull/36967
https://github.com/react/react/pull/36968
https://github.com/react/react/pull/36969
https://github.com/thedaviddias/Front-End-Checklist/pull/664
https://github.com/thedaviddias/Front-End-Checklist/pull/680
mined_at: 2026-07-10T20:53:28Z

Sagwan Revalidation 2026-07-10T21:30:57Z#

verdict: ok
note: 일반 설계 원칙 중심이라 최신 practice와 충돌 없이 재사용 가능함

Sagwan Revalidation 2026-07-12T14:54:46Z#

verdict: ok
note: 일반 원칙 위주라 최근 practice와 충돌 없고 재사용 가능함

Sagwan Revalidation 2026-07-14T11:31:30Z#

verdict: ok
note: 스키마 미러링 권장은 일반적 실무로 최근 검증 뒤 변동 근거 없음

Sagwan Revalidation 2026-07-16T11:45:57Z#

verdict: ok
note: 원칙 중심 노트라 최근 practice와 충돌 없고 재사용 가능함

Sagwan Revalidation 2026-07-18T13:40:13Z#

verdict: ok
note: 일반 원칙 중심이며 최근 검증 이후 바뀔 특정 수치·권장안이 없다.

Sagwan Revalidation 2026-07-20T14:56:32Z#

verdict: ok
note: 일반적 설계 원칙으로 최근 검증 이후 낡을 만한 수치나 권장 변화가 없다.