Retire contract-readiness flag after verified rollout

[devantler]

🤖 Generated by the Agentic Engineer

Remove the default-off contract-readiness release flag only after real rollout evidence establishes the probe's network vantage point, independent lifecycle, scoped Deployment observation, URL binding, outage/recovery, and stable resource usage. Part of #99.

• Record a reviewed production rollout and observed contract failure/recovery with the connector otherwise healthy.
• Verify monitor access, TLS trust, explicit egress, credential-free operation, and current output URL binding.
• Remove the OpenFeature flag and deployment switches in one change while preserving operational workload selection.
• Keep all reachability, controller boundary, and Kubernetes acceptance coverage passing.

Until this evidence exists, both controller observation and probe execution remain default-off. This issue does not authorize Platform activation.

[devantler]

🤖 Generated by the Agentic Engineer

The implementation is now released as v1.4.0 through #102, and #99 is closed. Use the verified immutable artifacts and acceptance evidence for the eventual reviewed rollout. All signatures bind to merged source 8ccd1ea44ba98ef170d4aec81f1abafff963ed40.

Both controller observation and probe execution remain default-off. The controlled Kubernetes and released-container tests passed, but the production acceptance criteria here remain unchecked and Platform activation is not implied.