No visible test for Windows path separators in launcher/CLI argument forwarding

Which version line?

v2 — current (@modelcontextprotocol/inspector@latest)

Which client?

CLI

Inspector version

2.7.0 (git tag) — static code-review finding, not run locally

Node version

N/A — static code review, no live run performed

Operating system (and browser, for the web client)

N/A — static code review

Transport

Not applicable / never connected

MCP server under inspection

N/A — this is a static code-review finding against the 2.7.0 tag source (clients/launcher/src/parse-launcher-argv.ts and CLI arg handling), not a live reproduction against a running MCP server.

Steps to reproduce

Found via static review of the 2.7.0 tag source, not a live run.

1. parseLauncherArgv and the CLI's arg handling work on raw argv slices.
2. Nothing in the reviewed tests exercises a Windows-style path with backslashes as a forwarded server command/arg.
3. The project's own history shows a "Windows CI/gate fixes" pass this cycle — worth confirming it covered argument content, not just the runner environment.

I have not run this on a Windows machine to observe an actual failure; flagging the absence of this test case itself.

Expected behavior

A test exists asserting that a Windows-style path with backslashes, passed as a forwarded server command or argument, survives launcher/CLI argument parsing intact.

Actual behavior

No visible test covers this case; the "Windows CI/gate fixes" pass this cycle appears to have addressed the runner environment but not necessarily argument content specifically.

Suggested fix: add a test case in the launcher/CLI argv-parsing suite that passes a Windows-style path (with backslashes) as a forwarded argument and asserts it round-trips correctly.

Logs, errors, or screenshots

No response

Already prototyped a fix?

No response

Before you submit

• I searched existing issues and this is not a duplicate.
• This is not a security vulnerability report (those go through the private advisory process).

Start with clients/launcher/src/parse-launcher-argv.ts and the CLI argument-handling code, then locate the launcher/CLI argv-parsing test suite. Add coverage for a Windows-style path with backslashes passed as a forwarded command or argument, and verify that it round-trips intact.