Production deployment activation hangs on managed Functions — upload completes in ~3s, polling times out at 10 min; all API-inclusive deploys affected; no platform incident

**Resource:** Static Web App `airgro-command-centre`, resource group `rg-airgro-prod`, **West Europe** (content endpoint `content-am2.infrastructure.1.azurestaticapps.net`), Standard SKU, GitHub-sourced from `main`.

### Symptom
Since ~13:50 UTC on 10 June 2026, every production deployment fails at the activation stage. The artifact **upload completes in ~3 seconds** ("Finished Upload. Polling on deployment"), then polling **times out after 10 minutes** ("Upload Timed Out. Unsure if deployment was successful or not."). Production content has not changed since the last successful deploy at 08:36 UTC despite ~8 attempts. The environment status sits at **Failed** (not In Progress) after each attempt.

### Isolation performed
- Deployments that **exclude** the managed API (`api/`) activate successfully in seconds (verified on a preview environment).
- Deployments that **include** the API hang identically — across **both** GitHub Actions (`Azure/static-web-apps-deploy@v1`) and the SWA CLI, on **both** production and preview environments.
- All 30 functions are `app.http` triggers; the `api/` folder changed by **one file (+8 lines)** since the last successful deploy.
- The currently-running app + API are healthy (`/api/health` → 200).
- Portal **Diagnose and solve problems** → Content Deployment and Configuration & Management troubleshooters both **error out** before completing ("Sorry, an error occurred. Please refresh the page and try again.").
- **No** Azure Service Health incident is posted for West Europe / Static Web Apps / App Service / Functions.

### Reference
DeploymentId `64c4aa68-4ba5-4216-aedb-0bcd3953e124`, content endpoint `content-am2.infrastructure.1.azurestaticapps.net`.

### Ask
Please investigate / clear the stuck managed-Functions deployment-activation state for this resource. The subscription is CSP-managed, so direct Microsoft technical support isn't available to us — hence raising it here.