Summary

MemoryQmdManager.ensureCollections() is meant to rebind a managed qmd collection (remove + re-add) when its filesystem root changes — for example when an agent's workspace is repointed. The rebind never fires, so collections stay pinned to the stale root after a workspace move.

Root cause

The rebind decision in shouldRebindCollection(collection, listed) compares listed.path against the desired collection path. But listed.path is always undefined:

• listCollectionsBestEffort() reads qmd collection list, whose output carries no filesystem path (only name / pattern / counts).
• With listed.path undefined, shouldRebindCollection takes its defensive "incomplete metadata" branch and returns false → no rebind.

So a configured workspace move is invisible to the engine: memory reads keep resolving the old location while the agent writes to the new one.

qmd collection show <name> does expose the path:

Collection: memory-dir
  Path:     /.../workspace/memory
  Pattern:  **/*.md

Reproduction

1. Point an agent at workspace A; let qmd index it.
2. Repoint the agent's workspace to B (same content).
3. Restart + memory index --force.
4. Observe: qmd store_collections still reference A; recall resolves A, not B.

Proposed fix

Enrich listCollectionsBestEffort() with each managed collection's path via qmd collection show <name>, so shouldRebindCollection can detect a changed root and rebind. (PR incoming.)