Thank you, but the issue isn't the deployment status itself — I can see it's marked READY. The problem is that the deployment doesn't actually serve any content: requesting the production URL returns a 404, and vercel inspect shows Builds: . [0ms] for both deployments (dpl_66ZLUohN6RTpvr4f3Rg2iTxJLV9o and dpl_Eifwg1RbCGDD99xNht13Cm3vvmQc), which suggests the build never actually got registered/activated despite the build log showing a successful compile.

Steps to reproduce:

1. curl -I https://connecta-mente.vercel.app/ → returns 404, even though the dashboard shows the deployment as Ready.
2. This happened on two separate accounts/teams (agencia-f4 and conectasaudepe) with the same project, ruling out account-specific state.
3. A second deploy attempt on the same project consistently gets stuck at UNKNOWN status indefinitely (not the 45-minute build timeout — it never even shows build progress).

Could someone from the platform/infra team take a look at why a READY deployment isn't actually being served at the edge?