Indexing repository unexpectedly indexes C:/Users/{USERNAME} instead of selected repo path (security/privacy risk)

[LeoTheLegion]

Summary:
When I index a specific repository in codebase-memory-mcp from VS Code, it appears to index C:/Users/{USERNAME} instead of the selected repository directory.

Why this matters:
This can unintentionally ingest unrelated local files outside the target repository, which is a privacy/security concern.

Environment:

1. OS: Windows
2. Install method: PowerShell installer
3. Client: VS Code (MCP integration)
4. Repository intended for indexing: specific workspace folder only

Steps to reproduce:

1. Install codebase-memory-mcp via PowerShell setup on Windows.
2. Use it in VS Code MCP.
3. Run index on a specific repository path.
4. Check resulting indexed project scope/name/content.

Expected behavior:
Only the provided repository directory is indexed.

Actual behavior:
Indexing scope resolves to C:/Users/{USERNAME} (or appears to include that directory), not just the selected repository.

Impact:
Potential accidental indexing of sensitive local data outside the intended repo.

[DeusData]

Verified fixed on v0.7.0. Indexing C:/cbmrepo in Windows CI (run) registers the project with root_path: "C:/cbmrepo" (the path I gave) and file nodes src/server.mjs / src/sub/calc.js — not C:/Users/.... The wrong-path scoping is gone (wide-char path handling, #386). Closing — this also removes the privacy concern of ingesting the home directory. Reopen if a specific path still resolves to the home dir on v0.7.0. 🙏