A merged campaign capability is not an activated campaign

A merged, deployed campaign capability is not active unless its live runtime configuration independently satisfies every fail-closed gate. For release readiness, inspect the deployment workflow to see whether it mutates configuration, then query the target environment for the exact enable flag, schedule, provider selector, and worker trigger; an example env template or a green required-env check does not prove an optional rollout flag is set. This method applies to runtime-configured rollouts and does not replace an end-to-end canary after enablement.