Under the hood
Skills-sync resync ticks now record why they fired and report when one is skipped after the machine slept too long.
What
The periodic scheduler that resyncs skills (packaged instruction sets Claude Code can load) now labels each resync tick with a trigger reason, either resync (a regular scheduled run) or wake_settle (following the machine waking from sleep). It also sends a new telemetry event, tengu_skills_sync_resync_skipped, when a resync tick is skipped because the machine had been asleep too long.
Why
This makes it possible to tell, from telemetry, whether skills stayed in sync correctly across sleep/wake cycles, and to see when a resync was skipped rather than assuming it always ran.