Plugin binaries are cached and verified by hash, and flaky downloads retry automatically.
What's wrong with this entry?
Downloaded plugin binaries now land in a cache entry named by their sha256 and verified against it, staged in a temporary directory first and written with restrictive permissions, then swept on a time-to-live. Transient download failures retry on a backoff schedule bounded by a deadline.
- Staging directories are prefixed
.binary-staging-. - The hashed-storage path is conditional; a direct filesystem fallback is retained.
- Storage failures are wrapped in a distinctly named error rather than surfacing raw.
.binary-staging-
Strings lifted out of the shipped bundle, so the claim above can be checked against them.