Make Releases own the promotion workflow instead of splitting it across stale queue aliases, orphaned promotion routes, and approval-only entry points.
Keep approvals as the adjudication surface, but move promotion list, create, and detail flows under one canonical subtree.
The release workbench opens /releases/promotions/create with:
releaseId
returnTo
The promotion wizard treats this as a first-class release-context launch:
preloads environments for the supplied release
advances directly to target selection once release identity is known
keeps a return path back to the originating release or run context
The wizard’s Gates step states that gates are evaluated when the request is decided. Its former Open Decisioning Studio action was withdrawn (CCP-028): it opened a gate review page that showed fixed gate results for every release. The recorded per-gate verdicts are on the approval record.
