[Windows] v0.9.0 install never adds `~/.local/bin` to the user PATH — appends bash `export PATH=...` to `~/.profile` and prints a misleading "PATH already includes

[cyberlieflife]

Version

codebase-memory-mcp 0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

After a successful install, the codebase-memory-mcp command cannot be run from a new terminal:

PS C:\Users\cyber> codebase-memory-mcp --version
codebase-memory-mcp : 无法将“codebase-memory-mcp”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。
CommandNotFoundException

The installer prints PATH already includes C:/Users/cyber/.local/bin and instructs the user to run source C:/Users/cyber/.profile, but on Windows:

• cbm_detect_shell_rc() (src/cli/cli.c, lines 198–235) never matches the SHELL env var against /zsh, /bash, or /fish on Windows, so it falls back to ~/.profile.
• cbm_ensure_path() (lines 2299–2348) has no _WIN32 branch: it appends the bash line export PATH="C:/Users/cyber/.local/bin:$PATH" to C:\Users\cyber\.profile. PowerShell and CMD do not read .profile, so the user PATH is never actually updated — no write to HKCU\Environment\Path.
• The PATH already includes ... message is decided by checking whether that exact line already exists in the rc file (cbm_ensure_path returning CLI_TRUE), not by inspecting the real PATH environment variable — so it is misleading on Windows.

Expected: on Windows the installer adds %USERPROFILE%\.local\bin to the user PATH via the registry (e.g. setx or [Environment]::SetEnvironmentVariable("Path", ..., "User")) and prints a PowerShell-appropriate message instead of source ~/.profile.

Reproduction

1. Fresh Windows 11 machine, run install.ps1 from the v0.9.0 release archive.
2. Note the output PATH already includes C:/Users/xxx/.local/bin and Restart your shell or run: source C:/Users/xxx/.profile.
3. Open a new PowerShell or CMD window.
4. Run codebase-memory-mcp --version → CommandNotFoundException.
5. Inspect C:\Users\xxx\.profile → it contains # Added by codebase-memory-mcp install and export PATH="C:/Users/xxx/.local/bin:$PATH".
6. Run [Environment]::GetEnvironmentVariable("Path", "User") → C:\Users\xxx\.local\bin is absent.

Logs

PATH already includes C:/Users/xxx/.local/bin
Install complete. Restart your shell or run:
  source C:/Users/xxx/.profile
PS C:\Users\xxx> codebase-memory-mcp --version
codebase-memory-mcp : 无法将“codebase-memory-mcp”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写，
如果包括路径，请确保路径正确，然后再试一次。
所在位置 行:1 字符: 1
+ codebase-memory-mcp --version
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (codebase-memory-mcp:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[AmirF194]

Also doesn't reproduce against current main (0d6f26a). The install flow no longer touches .profile on Windows at all: cbm_ensure_path() (the bash-rc-file writer you quote, src/cli/cli.c:5697) is only called from the non-_WIN32 branch of the install path. Under #ifdef _WIN32 it instead calls cli_ensure_windows_user_path() (src/cli/cli.c:5873, wired in at :9246), which opens HKEY_CURRENT_USER\Environment via RegOpenKeyExW/RegQueryValueExW and does a real RegSetValueExW append to the user Path value, no .profile/source involved.

Same root cause and same fix commit as #1456: git show v0.9.0:src/cli/cli.c | grep -c cli_ensure_windows_user_path is 0, the function doesn't exist in the tag matching your reported version. It was added in 0e00ef57 (2026-07-16, "feat: coordinate concurrent CBM sessions") and is present in v0.9.1-rc.1 and every commit since. v0.9.0 (2026-07-08) is still the Latest release tag, so this is a shipped-vs-fixed gap rather than something live on main to patch.