Production Bing validation exposed HTTP 500 at the external root proof because TLS termination was followed by an internal rewrite using the wrong protocol. This release corrects that rewrite boundary, but remains unverified until the external proof returns HTTP 200, the automatic submission runs, a later canary returns HTTP 200, and the idempotent rerun passes.
What changed
01
Recorded the production Bing validation failure as an external root-proof HTTP 500 instead of treating the earlier request result as successful verification.
02
Traced the failure to a protocol mismatch between TLS termination and the internal proof rewrite, rather than to the public root filename or production key.
03
Corrected the internal rewrite protocol boundary while preserving the exact public root-proof contract and keeping the production key server-only.
04
Requires an external proof HTTP 200, the automatic submission, a subsequent changed-URL canary HTTP 200, and an unchanged idempotent rerun before declaring the integration operational; this release makes no advance claim of success, crawling, or indexing.