Explain the mismatch between local Email health and Kubernetes probes #5421

🤖 Generated by the Agentic Engineer

Problem

The reviewed production observer reports local health while Kubernetes remains unready and continues restarting Email. The exact-version synthetic control answers both health paths within the existing deadline. These observations do not identify the production cause.

Acceptance

• Extend the opt-in, main-only bounded observer to compare the existing health request paths and target without changing probes, network rules, application configuration or retained data.
• Read only the application's allowed/blocked address classifications using its existing administrative identity inside the protected workflow. Keep credentials, addresses, raw responses and native errors out of logs and artifacts; use finite reads, strict response validation and stable identity/input bindings.
• Demonstrate success, actual blocked-state detection and incomplete/malformed/failure controls against the exact supported application behavior. Missing evidence remains inconclusive.
• Merge through protected validation and review, observe a bound production result, and retain Restore Email availability after repeated startup failures #5412 until a root-cause repair produces sustained availability and authenticated administration.

Part of #5412