{"version":"2.1.277","anchor":"directory-sync-now-writesreads-a-git-keep-marker-file-to-de","canonical_anchor":"directory-sync-now-writesreads-a-git-keep-marker-file-to-de","heading":"Directory-sync now writes\/reads a git-keep marker file to detect prior sync state","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/directory-sync-now-writesreads-a-git-keep-marker-file-to-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Directory-sync now writes\/reads a git-keep marker file to detect prior sync state\n\nDirectory sync writes a small marker file to detect whether a folder was previously synced\n\n**What**\n\nDirectory sync now reads and writes a small JSON marker file inside a synced directory, recording a version number and the time it was written. It's created exclusively so it can't silently overwrite an existing one, and failures to read or write it are logged. A companion piece of logic also maps the various reasons directory sync can detach from a folder (commit not held, not in history, on another branch, branch switched, switched off, diverged, machine stopped) to explanations shown to the user.\n\n**Why**\n\nThe marker file lets directory sync detect whether a folder was already under sync before, which helps it behave correctly across restarts, while the clearer detach-reason mapping means users get a specific explanation instead of a generic one when sync stops.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}