Appwrite Cloud reports stale 12.8 GB storage after deployment cleanup and blocks Sites

### 👟 Reproduction steps 1. Use an Appwrite Cloud Free organization with a Git-connected Appwrite Site. 2. Delete old large Site deployments. In this case they were deleted on Thursday and the Site became available again. 3. Confirm the project has no Functions and no Storage buckets. 4. Confirm only three Site deployments remain: 184 MB, 183.9 MB and 183.7 MB (about 552 MB total). 5. Open organization Usage. Storage still reports 12.8 GB / 2 GB (642%). 6. Create and activate one new Site deployment. 7. The public Site becomes unavailable and returns HTTP 402 with router_limit_exceeded. 8. The discrepancy persists for several days after the old deployments were deleted. ### 👍 Expected behavior Storage usage should be recalculated from the resources that still exist. With roughly 552 MB of visible Site deployments and no Functions or Storage buckets, the project should be below the 2 GB Free limit and the active Site should remain publicly available. ### 👎 Actual Behavior Organization Usage reports 12.8 GB / 2 GB even though the visible deployments total about 552 MB. The active Site is blocked with HTTP 402: {"type":"router_limit_exceeded","message":"This project has reached its resource limit."}. The Site briefly worked after cleanup but was blocked again after a new deployment. ### 🎲 Appwrite version Appwrite Cloud ### 💻 Operating system Linux ### 🧱 Your Environment Appwrite Cloud Free plan; GitHub-connected Appwrite Sites; Next.js application. The issue appears to be stale or hidden deployment/build storage accounting. No project ID or private account information is included in this public report. ### 👀 Have you spent some time to check if this issue has been raised before? - [x] I checked and didn't find similar issue ### 🏢 Have you read the Code of Conduct? - [x] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)