{"version":"2.1.247","anchor":"memory-path-resolution-calls-a-warm-up-step-that-currently-d","canonical_anchor":"memory-path-resolution-calls-a-warm-up-step-that-currently-d","heading":"Memory path resolution calls a warm-up step that currently does nothing","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/memory-path-resolution-calls-a-warm-up-step-that-currently-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Memory path resolution calls a warm-up step that currently does nothing\n\nMemory path lookups call a new warm-up step that currently does nothing at all.\n\n**What**\n\nSeven places that touch auto-memory, including the memory file watcher and the memory tool, now await a new warm-up call before resolving paths. Its body immediately resolves and nothing ever fills the canonical workspace root it is meant to prime, so path resolution still falls back to the existing git-root lookup.\n\n**Details**\n\n- The resolver gained fields for the canonical root, a per-project map of it, and the warm-up promise, plus a latch cleared on reset.\n- The per-project lookup feeds the project-directory hash but always returns undefined in this build.\n- No flag involved; the call sites shipped ahead of the implementation.\n\n**Evidence**\n\n`warmCanonicalWcRoot`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}