{"version":"2.1.219","anchor":"team-memory-mount-conflicts-fail-closed-on-write-and-recover","canonical_anchor":"team-memory-mount-conflicts-fail-closed-on-write-and-recover","heading":"Team-memory mount conflicts fail closed on write and recover automatically","tier":"notice","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/team-memory-mount-conflicts-fail-closed-on-write-and-recover","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Team-memory mount conflicts fail closed on write and recover automatically\n\nShared team memory mounts stop clobbering each other and switch back on once a conflict clears.\n\n**What**\n\nWriting a store manifest into a shared mount is now race-safe, and a mount suppressed for a conflicting manifest re-enables itself once the conflict is gone.\n\n**Details**\n\n- Manifest writes into an absent non-user mount stage to a temp file and hard-link into place, so a racing store cannot be overwritten.\n- Finding another store's manifest at write time throws rather than proceeding.\n- Mounts suppressed as `mount_dir_foreign_partition` or `mount_dir_unmanifested_nonempty` are re-adopted automatically, emitting `tengu_team_mem_foreign_partition_recovered`.\n- Write-time guidance strings were rewritten to name the conflicting directory and state that sync re-enables itself.\n\n**Evidence**\n\n`mount dir holds another store's .memory-sync manifest at write time (fail closed)`\n\n- Area: Team Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}