{"version":"2.1.265","anchor":"directory-sync-git-worker-internal-rework-basis-memoized-in","canonical_anchor":"directory-sync-git-worker-internal-rework-basis-memoized-in","heading":"Directory-sync git worker internal rework (basis-memoized index\/worktree checks, session-tagged 'kept' ref)","tier":"internal","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/directory-sync-git-worker-internal-rework-basis-memoized-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Directory-sync git worker internal rework (basis-memoized index\/worktree checks, session-tagged 'kept' ref)\n\nDirectory sync's internal git worker was reworked with memoized checks and session-tagged 'kept' refs\n\n**What**\n\nThe background worker that handles git operations for directory sync had its internal logic reshuffled. It now uses two new memoized (cached) helper functions to check whether a git \"basis\" (a known starting point) matches a given commit, or matches a given index and working-tree state, and a new function tags a git ref by session ID as \"kept\" before falling back to discarding a temporary index.\n\n**Why**\n\nThis is an internal restructuring of directory sync's git handling; the finding doesn't indicate a user-visible behavior change beyond how these checks are computed internally.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}