{"version":"2.1.219","anchor":"org-memory-root-mount-defends-its-own-name","canonical_anchor":"org-memory-root-mount-defends-its-own-name","heading":"Org memory root mount defends its own name","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/org-memory-root-mount-defends-its-own-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Org memory root mount defends its own name\n\nOrg memory setup renames aside anything squatting its mount name rather than colliding.\n\n**What**\n\nDeriving the org-memory root mount now updates an existing entry in place and renames aside any other config that has taken the derived mount name, instead of colliding with it.\n\n**Details**\n\n- The prompt index is taken from the server config, falling back to a default and reporting `prompt_index_absent`.\n- A discovered config squatting the derived mount name is renamed aside, logged as \"org-memory-discovery: discovered config squatting the derived mount name\".\n- New event `tengu_org_memory_root_mount_derived` records the mount name, mode and prompt-index source.\n- Runs on the org-memory discovery path; whether that feature is enabled in this build was not determined.\n\n**Evidence**\n\n`org-memory-discovery: discovered config squatting the derived mount name`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}