# Workstation download recovery · 2026-10-13

The prior Hugging Face startup failed after a network interruption. Its exact historical HTTP cause was not recorded. Current isolated probes verify valid CDN headers and matching asset bytes; the confirmed application defect was missing bounded transfer recovery.

All three large resources now share a downloader with a 30-second idle timeout, a 120-second total deadline per resource, and at most three total attempts. Temporary transport errors retry; invalid digests, sizes and destinations remain errors. The UI reports progress and supports reload after terminal failure. The engine is fetched as a 2,543,112-byte gzip instead of 10,370,402 raw bytes (75.48% reduction); decoded bytes match the original engine SHA-256.

- Browser fault injection: each first large download aborted, then exactly one retry recovered. Real native controls, shoe impulse and receipt passed. Persistent geometry failure stopped after three attempts; manual reload recovered.
- Local full UI: drag, numeric coordinates, gripper, nudge, reset, reachability state, receipt, and 1440/390/320-pixel layouts passed with no unexpected page or response errors.
- Native contract/export tests: 19 passed. JS and publication regression outputs are retained in regression-tests.json.
- Exact engine/controller code, native XML, original WASM, all meshes, renderer geometry and physics metadata remain unchanged. Runtime provenance lists the original hashes.

These are download-recovery and browser-functional results, not new shoe-grasp or physical-robot qualifications. Local timing does not predict public CDN or device performance. Public deployment verification takes place after this evidence is frozen; the historical failure is retained in prior-public-failure.json.