fix: discover .vscode-server workspaceStorage dirs for WSL / Remote SSH / devcontainer

[hora7ce]

Description

Fixes the dashboard showing "No Copilot chat log directories found" when the extension is used via VS Code Server (WSL2, Remote SSH, Dev Containers).

When VS Code connects to a remote host, it runs as a server and stores all workspaceStorage under:

~/.vscode-server/data/User/workspaceStorage
~/.vscode-server-insiders/data/User/workspaceStorage

findVsCodeDirs() only scanned the desktop installation paths (~/.config/Code, AppData, ~/Library/...) and never checked these server paths, so the extension found no sessions.

Changes

• findVsCodeDirs() — scan ~/.vscode-server and ~/.vscode-server-insiders on non-Windows platforms
• harnessFromPath() — add .vscode-server-insiders and .vscode-server checks (most-specific first to prevent the Insiders path matching the plain .vscode-server substring), returning 'Local Agent (Server)' / 'Local Agent (Server Insiders)' instead of falling through to 'Local Agent'
• Tests — three new cases covering both server editions and the substring-ordering invariant

Related Issues

Fixes #62

Checklist

• npm run check passes (typecheck + lint + spellcheck + knip + tests)
• Changes are covered by tests
• Documentation updated (n/a — no user-visible doc change required)

[hora7ce]

@microsoft-github-policy-service agree

[san360]

Nice fix — the logic is correct, tests are well-structured, and there are no security concerns. A few items to address before merging:

Required: Documentation Updates

This PR introduces two new harness names (Local Agent (Server) and Local Agent (Server Insiders)) that will appear in the dashboard UI, but the docs don't mention them. Please update:

1. README.extension.md — Add two rows to the "Supported Harnesses" table:
   | Local Agent (Server) | ~/.vscode-server/data/User/workspaceStorage/ |
   | Local Agent (Server Insiders) | ~/.vscode-server-insiders/data/User/workspaceStorage/ |

2. docs/content/getting-started/supported-tools.md — Under the "Local Agent (VS Code and VS Code Insiders)" section, add a note that when VS Code connects via Remote-WSL, Remote-SSH, or Dev Containers, logs are stored at ~/.vscode-server/data/User/workspaceStorage/ and shown as "Local Agent (Server)" in the dashboard.

3. docs/content/_index.md — Add Local Agent (Server) / Local Agent (Server Insiders) to the multi-harness table.

Nit: Add ordering comment in harnessFromPath() (non-blocking)

The substring collision between .vscode-server and .vscode-server-insiders relies on check ordering. A short comment would prevent a future contributor from accidentally reordering:

// Check .vscode-server-insiders BEFORE .vscode-server — the latter is a
// substring of the former and would match incorrectly if checked first.
if (logsDir.includes('.vscode-server-insiders')) return 'Local Agent (Server Insiders)';
if (logsDir.includes('.vscode-server')) return 'Local Agent (Server)';

Nit: Explain the platform guard (non-blocking)

// VS Code Server only runs on the remote host (Linux/macOS), not on Windows directly
if (process.platform !== 'win32' && home) {

Nice-to-have: findVsCodeDirs() test coverage

The new tests cover harnessFromPath() (string matching) but not findVsCodeDirs() itself. A test that mocks fs.existsSync to verify the server paths are included (and excluded on Windows) would strengthen confidence.

---

Overall this is a solid, well-scoped fix. The code and security posture look good — just needs the doc updates to be complete. 👍