Cross-machine file sync now reports five new events covering disagreement, mid-turn sync and file handoff.
What's wrong with this entry?
Sync between machines now reports a barrier event plus events for frame disagreement, mid-turn sync, and publishing or taking in files between tool calls. The barrier event records whether both sides agree on file state ("up", "down" or "both"), why they do not (peer too old, peer stale, no frame of our own, peer does not take files), plus timing and event counts. Reason strings pass through an allow-list that maps anything unrecognised to "other".
- No gate; emitted inside a try/catch on the sync path.
tengu_dir_sync_barrier
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