{"version":"2.1.267","anchor":"multi-store-memory-sync-now-recognizes-tombstones-and-wont","canonical_anchor":"multi-store-memory-sync-now-recognizes-tombstones-and-wont","heading":"Memory sync now recognizes tombstones and won't silently resurrect deleted content","tier":"notice","area":"Memory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/multi-store-memory-sync-now-recognizes-tombstones-and-wont","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Memory sync now recognizes tombstones and won't silently resurrect deleted content\n\nWriting or syncing memory files that were deliberately deleted elsewhere now surfaces a clear tombstone conflict instead of silently recreating them\n\n**What**\n\n- When a memory write conflicts because the target was recently deleted elsewhere (a \"tombstone\"), it's now detected and reported as a distinct `tombstone_conflict` reason rather than a generic conflict.\n\n- Multi-store (org\/shared) memory sync checks for this on push: if a local copy predates the deletion and is old enough, it's silently deleted to match; otherwise the user is warned once per path instead of the file being endlessly re-pushed or silently recreated.\n\n- Writing identical content back to a path that was just tombstoned is now explicitly refused with a dedicated error rather than going through generic conflict handling.\n\n- The conflict-error type used for memory version conflicts now carries `tombstone` and `deletedAtMs` fields (with a matching `deleted_at`\/`conflicting_memory_id` schema addition), including a fallback check for older messages that mark the conflict via a `(tombstone_conflict)` suffix.\n\n**Why** Without this, deleting a shared memory entry on one machine could get silently undone when another machine's stale local copy synced back up. Now the conflict is detected and surfaced clearly, so a deletion actually sticks instead of being fought over by out-of-date copies.\n\n- Area: Memory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}