{"version":"2.1.265","anchor":"directory-sync-git-worker-gains-mid-turn-shipping-and-a-stre","canonical_anchor":"directory-sync-git-worker-gains-mid-turn-shipping-and-a-stre","heading":"Directory sync engine reworked for mid-turn shipping and generation tracking","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/directory-sync-git-worker-gains-mid-turn-shipping-and-a-stre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Directory sync engine reworked for mid-turn shipping and generation tracking\n\nDirectory sync now ships changes mid-turn and tracks whether an uploaded generation has been acknowledged\n\n**Unclear.** The exact trigger conditions for mid-turn shipping and what consumes the streaming change feed are not stated.\n\n**What**\n\nThe directory-sync engine, which keeps a cloud\/remote session's checkout in step with changes on the user's machine, was substantially restructured:\n\n- A new handler tracks whether a generation is \"owed\" (uploaded but not yet acknowledged or refused by the sync service), and notifies the user distinctly for a \"refused\" case versus a \"not taken\" case.\n\n- Progress past a \"not_published\" state now only proceeds at defined turn boundaries (`turn_end`\/`turn`).\n\n- Snapshotting and shipping changes is now parameterized by a \"point\" in the turn, including `turn_end` and `before_command`, tracked via a new `midTurnShip` concept, so changes can ship partway through a turn rather than only at the end.\n\n- The worker's returned interface now exposes a `streaming` field wired to a change feed, started as part of the worker setup.\n\n**Why**\n\nThis makes directory sync more responsive, shipping changes at more points during a turn instead of waiting until the end, while giving the user clearer feedback when an upload is refused versus simply not yet taken.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}