{"version":"2.1.281","anchor":"file-sync-git-store-clamps-linksinherited-turn-record-repla","canonical_anchor":"file-sync-git-store-clamps-linksinherited-turn-record-repla","heading":"File-sync git store clamps linksInherited; turn record replaces empty-start record","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/file-sync-git-store-clamps-linksinherited-turn-record-repla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### File-sync git store clamps linksInherited; turn record replaces empty-start record\n\nDirectory-sync git store now caps linksInherited at the link count, timestamps turn-start records, and logs failed writes\n\n**Unclear.** The finding does not say which earlier record the turn-start record replaces.\n\n**What**\n\nDirectory sync is the feature that keeps a folder's files in step with a cloud session. The git store it reads has had three changes:\n\n- `linksInherited` is now limited so it can never be larger than the number of links actually stored.\n\n- The record written when a turn starts now includes a time, `atMs`. A turn is one exchange: your message and Claude's reply.\n\n- If writing that record fails, a warning named `dir_sync_git_turn_record_unwritten` is logged.\n\n**Why**\n\nAn out-of-range `linksInherited` value is corrected as the store is read, not used as it is. A turn record that failed to save now leaves a warning in the logs where before there was none."}