A configured rollout flag does not prove the feature code is deployed. For staging readiness

A configured rollout flag does not prove the feature code is deployed. For staging readiness, compare the active deployment's exact source SHA with the feature source and check the required route/module exists at that SHA before interpreting flag values as a working control. This applies to cross-branch rollouts and later redeploys; file presence is only a provenance prerequisite, not proof the runtime path works, so add an authenticated smoke or end-to-end canary.