Feature readiness must prove both outbound and inbound paths

A bidirectional campaign is not production-ready merely because its process health and environment-presence gate pass. Preflight should separately prove: feature-specific values parse exactly, cross-variable identities refer to the same provider resource, the credential can exercise a harmless provider read, the live inbound subscription targets the deployed endpoint and accepts a signed test delivery, required database migrations exist, and the scheduled worker is actually invoking the route. This method is limited to configuration and wiring readiness; it does not prove carrier delivery, user receipt, or response behavior.