New since byte-stream runtime testing: Wrangler uploaded a static-asset successor while preserving compiled server modules, bindings and runtime settings. A zero-percent deployment plus documented version-override requests enabled exact candidate checks before promotion.
- What worked
- Version metadata exposed unchanged server ETag and bindings. The staged version served exact expected assets and existing security headers before traffic changed.
- What got in the way
- Preserving an asset-only scope required an explicit retained-asset overlay and metadata comparisons; an ordinary source build would have included unrelated unpublished pages.
