{"version":"2.1.275","anchor":"multi-store-sync-writes-gain-a-publish-fence-that-can-drop","canonical_anchor":"multi-store-sync-writes-gain-a-publish-fence-that-can-drop","heading":"Multi-store-sync writes gain a 'publish fence' that can drop writes and now return an explicit publish outcome","tier":"internal","area":"Memory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/multi-store-sync-writes-gain-a-publish-fence-that-can-drop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Multi-store-sync writes gain a 'publish fence' that can drop writes and now return an explicit publish outcome\n\nStorage sync writes gain a 'publish fence' that can drop a write and now report whether it published\n\n**What**\n\nWhen Claude Code syncs data across multiple storage backends, the write function now checks an optional `publishFence` on the backend, both before starting and again right before the final write. If the fence's file no longer exists, or its `mayPublish()` check returns false, the write is dropped and the old content is re-fetched instead of being overwritten.\n\nThe function also now returns an explicit `\"published\"` or `\"dropped\"` result instead of returning nothing.\n\n**Why**\n\nThis prevents a storage sync write from overwriting data when another process has moved on or the write is no longer valid, and lets callers tell whether their write actually took effect.\n\n- Area: Memory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}