Before using an existing deployment workflow for a new candidate, verify both artifact

Before using an existing deployment workflow for a new candidate, verify both artifact inclusion and branch-to-environment mapping. A workflow that deploys successfully may omit an ignored/private experiment entirely, and a non-staging fallback can send a manual feature-branch dispatch to production. Treat deployment authorization as permission for the intended component and target, not permission to guess either.