Custom domain stuck in VALIDATING_OWNERSHIP and the certificate never issues, despite DNS being fully converged and verified.

Domain: staging.dentoryai.ashburtonfamilydental.com.au

Project: dentoryai (e6604ce1-0d17-410b-be26-9724e2e11702) — staging environment, dentoryai service, port 8080

Edge: edge-6705e5cc5ae5e82ae931d2b1f900f08f

Evidence the config/DNS is correct:

• DNS converged and stable: currentValue == requiredValue == 7z1e6q7f.up.railway.app, DNS_RECORD_STATUS_PROPAGATED (verified on public resolvers and via your API). Old target's 3600s TTL fully drained; stuck for hours past that.
• ACME path reaches your edge: http://staging.dentoryai.ashburtonfamilydental.com.au/.well-known/acme-challenge/ returns Server: railway-edge, 404, POP europe-west4-drams3a — identical behaviour to our working prod domain.
• No CAA block on the zone; domain attached exactly once (deleted=null, sync=ACTIVE); certificateErrorType and certificateErrorMessage are both null — no error ever surfaced.
• Sibling prod domain dentoryai.ashburtonfamilydental.com.au on the SAME edge has a VALID cert, so the edge and zone are proven healthy.
• During this window your GraphQL API (backboard.railway.com) intermittently returned Not Authorized with code INTERNAL_SERVER_ERROR on valid tokens, suggesting backend degradation. We also note incident OC3DGTST (image registry) occurred the same day; our stall continued past its resolution.

Already tried: one clean remove/re-add of the domain (which minted the new 7z1e6q7f target — DNS was updated and fully converged to it). The validation job appears wedged server-side. Please re-trigger ownership validation for this domain/edge.