Container panic 'Could not find file /home/site/wwwroot/output.tar.gz' on appsvc/python:3.11_20260203.2.tuxprod

## Summary Azure App Service Linux Python 3.11 deploys are failing at container start because the build phase produces `output.tar.zst` while the runtime `PythonStartupScriptGenerator` looks for `output.tar.gz` and panics. ## Environment - Image tag: `appsvc/python:3.11_20260203.2.tuxprod` - Oryx version (per build log): `0.2.20251017.2` - Deploy method: GitHub Actions OIDC -> OneDeploy (zip) - Date observed: 2026-05-08 / 2026-05-09 (UTC) - Customer App Service name (for cross-reference): `wapd-image-finder` ## Symptoms 1. GitHub Actions build step succeeds. 2. OneDeploy returns HTTP 200. 3. Container never serves traffic. 4. `/home/LogFiles/<latest>_docker.log` shows: ``` panic: Could not find file /home/site/wwwroot/output.tar.gz ``` 5. `oryx-manifest.toml` written by the build phase references `output.tar.zst` (zstd-compressed), not `output.tar.gz`. ## Apparent root cause A mismatch between the build-time compression format (zstd) and the runtime extractor's expected format (gzip). The `PythonStartupScriptGenerator` in this image tag does not appear to handle `.tar.zst` artifacts. ## Workaround being tested Setting `COMPRESS_DESTINATION_DIR=false` as an app setting (folk wisdom — not officially documented as controlling format selection). Results pending; will update. ## Ask - Confirmation whether this is a known regression in `3.11_20260203.2.tuxprod`. - Documented env var or version pin to roll back to a known-good earlier image while a fix lands. - Whether `PythonStartupScriptGenerator` in this image is intended to support zstd artifacts (and is broken), or whether the build-phase format selection is wrong.