{"version":"2.1.248","anchor":"five-new-telemetry-events-for-cross-machine-file-sync","canonical_anchor":"five-new-telemetry-events-for-cross-machine-file-sync","heading":"Five new telemetry events for cross-machine file sync","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/five-new-telemetry-events-for-cross-machine-file-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Five new telemetry events for cross-machine file sync\n\nCross-machine file sync now reports five new events covering disagreement, mid-turn sync and file handoff.\n\n**What**\n\nSync 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\".\n\n**Details**\n\n- No gate; emitted inside a try\/catch on the sync path.\n\n**Evidence**\n\n`tengu_dir_sync_barrier`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}