{"version":"2.1.280","anchor":"dir-sync-records-now-carry-a-bounded-history-chain-with-chec","canonical_anchor":"dir-sync-records-now-carry-a-bounded-history-chain-with-chec","heading":"Dir-sync records now carry a bounded history chain with checksums","tier":"internal","area":"Directory Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/dir-sync-records-now-carry-a-bounded-history-chain-with-chec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Dir-sync records now carry a bounded history chain with checksums\n\nFolder sync records now keep a bounded history chain with checksums of past generations\n\n**What**\n\nSync-point records for directory sync now include a `chain` field that captures a bounded list of recent generations that were sent, each with its generation number, worktree commit, sha256 checksum, size, and delivery method (`via`). This is trimmed to a cap and sits alongside the existing `fastForwardedTo` list.\n\n**Why**\n\nKeeping a checksummed history of recent sync generations gives folder sync a way to verify or recover state more precisely than before.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}