Deleted Pages deployment hostname continues serving assets

### Which Cloudflare product?

Pages (Direct Upload)

### Wrangler version

4.120.0

### What happened?

A Pages deployment was deleted successfully and no longer appears in either `wrangler pages deployment list` or the Cloudflare Pages deployments API. More than 20 hours later, its hash-based `*.pages.dev` deployment hostname still returns HTTP 200 and serves the deployment's original static assets.

Retrying deletion with the original full deployment UUID now returns API error `8000009` (“The deployment ID you have specified does not exist”), while the deployment hostname remains live.

The current production deployment and custom domain are behaving correctly. I am withholding the account, project, deployment UUID, and hostname from this public issue because the stale deployment contains internal analytics exports. I can provide those details privately to a Cloudflare maintainer.

### Expected behavior

Deleting a Pages deployment should make its hash-based deployment hostname and assets unavailable, ideally returning 404, within a documented propagation window.

### Reproduction

1. Direct-upload a Pages deployment containing a uniquely identifiable static file.
2. Delete that non-current deployment using Wrangler or the Pages API.
3. Confirm it disappears from deployment listing.
4. Request `https://..pages.dev/`.
5. Observe that the deleted deployment may continue serving the file.

### Additional context

The project uses Pages advanced mode (`_worker.js`) and Direct Upload. The stale asset is served directly from the deleted deployment hostname. Repeating the DELETE request cannot invalidate it because the API considers the deployment nonexistent.

Comienza reproduciendo el caso de Direct Upload con Wrangler 4.120.0 y la Pages deployments API: elimina un deployment que no sea el actual, confirma que desaparece de los listados y, después, solicita su hostname de pages.dev basado en hash y su asset único. Compara la respuesta de DELETE con el comportamiento del hostname; se considera terminado cuando el hostname eliminado deja de servir el asset y devuelve la respuesta documentada de no disponibilidad dentro de la ventana de propagación.

Escrito por el modelo de indexación a partir del texto del issue.