Under the hood
Useful2 Signal3
Directory sync gained catch-up, hold and offline controls internally.
What's wrong with this entry?
Anonymous. No account, no email.
What
The sync handle gained catch-up, sync-point, capture-point, install hold and release, and an offline callback, all reporting "not running" when no sync engine is open. Draining now returns whether it succeeded, and the initial seed step can refuse while sync is still starting up.
Evidence
catchUp: async (e, r) =>
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