{"version":"2.1.257","anchor":"directory-sync-now-distinguishes-repository-left-outcome-a","canonical_anchor":"directory-sync-now-distinguishes-repository-left-outcome-a","heading":"Directory sync now distinguishes 'repository left' outcome and tracks unshipped turns","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/directory-sync-now-distinguishes-repository-left-outcome-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Directory sync now distinguishes 'repository left' outcome and tracks unshipped turns\n\nSync clearing reports a distinct repository-left result, and turns whose changes could not ship are marked unshipped.\n\nThe directory-sync git worker's clearing logic now returns a distinct `repository_left` result, carrying `setAsideIn`, `moved`, and `left` details, instead of folding this case into a generic `not_cleared`\/`REPOSITORY_LEFT` code. Turn records also gain an `unshipped` flag plus an `M.unshippedTurn` marker when a turn's changes couldn't be shipped, to support later retry or reporting.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}