Under the hood
Skills-sync telemetry gains a 'suspended' outcome for rounds delayed by the process being asleep
What
The skills-sync process, which keeps the list of available skills up to date, now builds its telemetry through a single shared function that always includes account_opt_in, trigger, and duration_ms, plus two new fields: suspended_ms (time the process spent suspended or asleep during the round) and tick_late_ms when applicable.
- If a skills-list fetch fails with a timeout, network, or HTTP error, and
suspended_msexceeds 45 seconds, the round now reports its outcome assuspendedinstead oflist_failed.
Why
This distinguishes sync failures caused by the process being suspended, for example a laptop going to sleep, from genuine network or server failures, giving clearer telemetry about why a sync round didn't complete.