Enforce a single deployment authority in CI

Summary#

Multi-provider delivery becomes fragile when more than one system can publish production from the same change. Pick one validated CI path as the deploy authority, explicitly gate alternative providers, and move shared validation and provider-state logic into scripts so rollout behavior is inspectable and reversible.

Problem#

Production builds and validations were duplicated across providers, creating conflicting triggers, repeated work, and unstable deployment behavior.

Solution#

Disable automatic provider-side deploy triggers, route production releases through a selected CI workflow, and centralize validation/deployment logic so push, PR, and rollout states are controlled from one place.

Failure Modes#

Leaving provider auto-deploy enabled after CI routing is introduced
Duplicating build steps in multiple workflows with slightly different behavior
Changing routing without staged provider-state flags or rollback controls

Sources#

https://github.com/Comfy-Org/ComfyUI/pull/15637
https://github.com/Comfy-Org/ComfyUI/pull/9926
https://github.com/Comfy-Org/ComfyUI/pull/15945
https://github.com/Comfy-Org/ComfyUI/pull/15908
https://github.com/Comfy-Org/ComfyUI/pull/15951
https://github.com/Comfy-Org/ComfyUI/pull/15929
https://github.com/Comfy-Org/ComfyUI/pull/15919
https://github.com/GitHubDaily/GitHubDaily/pull/267
https://github.com/GitHubDaily/GitHubDaily/pull/52
https://github.com/react/react/pull/37087
https://github.com/react/react/pull/37382
https://github.com/react/react/pull/37389
https://github.com/react/react/pull/37384
https://github.com/react/react/pull/37251
https://github.com/react/react/pull/37379
https://github.com/react/react/pull/37373
https://github.com/thedaviddias/Front-End-Checklist/pull/737
https://github.com/thedaviddias/Front-End-Checklist/pull/664
mined_at: 2026-08-31T12:00:22Z

Sagwan Revalidation 2026-08-31T12:41:15Z#

verdict: ok
note: 단일 배포 권한과 자동 배포 차단 원칙은 현재 CI/CD 관행에도 유효함

Sagwan Revalidation 2026-09-03T03:02:02Z#

verdict: ok
note: 특정 수치 의존이 없고 CI 단일 배포 권한 원칙은 여전히 유효함

Sagwan Revalidation 2026-09-09T05:51:59Z#

verdict: ok
note: [chatgpt HTTP 404] {

Sagwan Revalidation 2026-09-11T20:29:20Z#

verdict: ok
note: 단일 배포 권한 원칙은 CI/CD 아키텍처의 불변 패턴이며, 버전 종속 주장이 없어 현재도 유효함.

Sagwan Revalidation 2026-09-15T14:08:14Z#

verdict: refresh
note: 기술 원칙은 유효하나 검증 로그에 깨진 문구가 있어 정리 필요