🐛 Sites: a domain only ever serves its *first* deployment — activating a new deployment doesn't change what's served

### 👟 Reproduction steps 1. Create a static site: `appwrite sites create --site-id demo --framework vite --adapter static --output-directory "./" --fallback-file index.html` 2. Deploy build **A**: `appwrite sites create-deployment --site-id demo --code ./distA --activate true` → the domain serves **A** ✅ 3. Deploy build **B** (different content): `appwrite sites create-deployment --site-id demo --code ./distB --activate true` 4. `appwrite sites get --site-id demo` → `deploymentId = B`, `latestDeploymentStatus = ready`, `live = true` 5. `curl https://<domain>/` ### 👍 Expected behavior The domain serves build **B** (the active deployment). ### 👎 Actual Behavior The domain still serves build **A**. Evidence: - `sites get` reports the active `deploymentId` = **B**, but `curl -D - https://<domain>/` returns `X-Appwrite-Deployment-Id: <A>`. - This happens even on `X-Cache: MISS` / `Age: 0` (a fresh origin response, not an edge-cache hit), and with `Cache-Control: no-cache` / `Pragma: no-cache` request headers. - `appwrite sites update-site-deployment --site-id demo --deployment-id <B>` returns success and updates the metadata, but serving still stays on **A**. - Deleting deployment **A** (`sites delete-deployment`) makes the domain return **HTTP 404** — confirming the domain is pinned to **A**, not the active deployment. - Reproduced identically with a build-from-source site: a second deployment with a changed source string builds to `ready`, but the changed string never appears in the served bundle (served asset hash is unchanged). ### 🎲 Appwrite version Appwrite Cloud ### 💻 Operating system Linux ### 🧱 Your Environment - Appwrite **Cloud**, region **fra** (Frankfurt) - Appwrite CLI **22.6.1** - Site: `adapter: static`, `fallbackFile: index.html` - Also reproduced with a **build-from-source** site (`framework: vite`, `installCommand: npm install`, `buildCommand: npm run build`, `outputDirectory: ./dist`) ### 👀 Have you spent some…