Use compatibility shims and API cleanup only after checking real caller behavior

Summary#

Problem#

External producers or clients often use slightly different key formats or ignore optional parameters, so strict expectations or speculative cleanup can break working integrations.

Solution#

First audit actual client behavior. If real ecosystems emit alternate-but-equivalent formats, add a narrow compatibility mapping. If a parameter is truly unused, remove it from both route and spec only after confirming real callers already rely on the default behavior.

Failure Modes#

Breaking hidden integrations by assuming all callers follow the documented format.
Adding broad compatibility logic that introduces ambiguous precedence or masks bad inputs.
Deleting API surface without validating live client traffic and default semantics.

Sources#

https://github.com/Comfy-Org/ComfyUI/pull/14373
https://github.com/Comfy-Org/ComfyUI/pull/14216
https://github.com/Comfy-Org/ComfyUI/pull/13853
https://github.com/Comfy-Org/ComfyUI/pull/14349
https://github.com/Comfy-Org/ComfyUI/pull/14241
https://github.com/Comfy-Org/ComfyUI/pull/14363
https://github.com/Comfy-Org/ComfyUI/pull/14014
https://github.com/Comfy-Org/ComfyUI/pull/13400
https://github.com/Comfy-Org/ComfyUI/pull/14381
https://github.com/Comfy-Org/ComfyUI/pull/14368
https://github.com/Comfy-Org/ComfyUI/pull/14372
https://github.com/Comfy-Org/ComfyUI/pull/14371
https://github.com/GitHubDaily/GitHubDaily/pull/267
https://github.com/GitHubDaily/GitHubDaily/pull/52
https://github.com/fastapi/full-stack-fastapi-template/pull/2305
https://github.com/react/react/pull/36173
https://github.com/react/react/pull/36727
https://github.com/react/react/pull/36726
https://github.com/thedaviddias/Front-End-Checklist/pull/664
https://github.com/thedaviddias/Front-End-Checklist/pull/680
mined_at: 2026-06-10T16:20:46Z

Sagwan Revalidation 2026-06-10T17:05:00Z#

verdict: refresh
note: 권장안은 유효하나 fastapi/full 링크가 불완전해 출처 정리가 필요함

Sagwan Revalidation 2026-06-11T19:36:05Z#

verdict: ok
note: 호환성은 실제 호출자 확인 후 좁게 적용하라는 원칙은 여전히 유효함

Sagwan Revalidation 2026-06-12T19:48:41Z#

verdict: ok
note: 핵심 원칙은 여전히 유효하고 수치·시한 의존 정보가 없다