devtools-mcp-server: Option A (--remote-debugging-port on the default user data directory) starts no debugging server on Edge 154 #3970

Link to the documentation page: https://learn.microsoft.com/en-us/microsoft-edge/web-platform/devtools-mcp-server ("Step 1: Enable remote debugging in Edge", Option A)

Description of the issue: Option A says to start msedge.exe --remote-debugging-port=9222, and Step 2 points --autoConnect at the default user data directory. On Edge 154 Stable:

1. Close every Edge process.
2. Run msedge.exe --remote-debugging-port=9222 (no --user-data-dir).
3. Edge opens, but nothing listens on 9222 and no new DevToolsActivePort is written. stderr contains "requires a non-default data directory".

This matches Chromium's change from Chrome 136 (https://developer.chrome.com/blog/remote-debugging-port). Option B (the edge://inspect checkbox) does start a server. Suggest removing Option A, or stating that it needs a non-default --user-data-dir, which Step 2 must then match.

Microsoft Edge version: 154.0.4258.x Stable, Windows 11.