Automatic (connectivity-triggered) retry attempts charged against this
path. Distinct from retryCount, which logs EVERY failure (update
sweeps + manual retries included). The automatic budget must not be
consumed by ordinary interaction, or a scene that failed a few slices
offline would be past the cap before online ever fires — so only
markAutoRetryAttempt (called by the connectivity retry) bumps this.
Classified cause. Persisted so retry policy can tell a transient failure from a deterministic one — previously the kind was computed for logging and then thrown away, so a WASM trap was retried on every reconnect exactly like a 503.
Error information tracked for failed loaders.