{"version":"2.1.246","anchor":"shared-team-memory-tells-you-when-a-write-never-saw-the-shar","canonical_anchor":"shared-team-memory-tells-you-when-a-write-never-saw-the-shar","heading":"Shared team memory tells you when a write never saw the shared version","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/shared-team-memory-tells-you-when-a-write-never-saw-the-shar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Shared team memory tells you when a write never saw the shared version\n\nShared memory conflict notices now distinguish a write that never saw the shared copy.\n\n**What**\n\nConflict notices for shared team memory now separate a file written by a session that never had the shared copy from an ordinary two-writers-at-once conflict, and the notice left on disk says which happened. Pulls that would overwrite a locally changed file also raise the notice.\n\n**Details**\n\n- Recovered conflicts are counted under `tengu_team_mem_conflict_recovered`.\n- A delete that comes back 404 no longer drops local state outright: the path is listed again and the delete is retried on the next cycle if the entry is still there.\n- Part of the existing team memory sync; no new flag.\n\n**Evidence**\n\n`this session did not have the shared version of that file when it wrote it. `\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}