Under the hood
Useful1 Signal2
The directory-sync watcher now reports starts, stops, drops and per-sync outcomes as telemetry.
What's wrong with this entry?
Anonymous. No account, no email.
What
New events record when the watcher starts, stops or fails, how many change bursts and uploads it produced, how often it overflowed or dropped events, and the outcome of each sync point (shipped, unchanged, failed, kept here, not running) with timings and file counts.
Evidence
tengu_dir_sync_watch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory