write the vs code integration page

[carlos-granados]

Writes the VS Code integration page, following the User Guide section by section in the same shape as the PhpStorm page.

The one structural difference is stated up front: VS Code has no PHP debugging of its own, so the PHP Debug extension has to be installed. Links to the Marketplace listing and the repository sit at the top.

Everything is taken from the extension's package.json and README rather than assumed, and all five VS Code documentation anchors were checked to exist on the live page:

• the generated Listen for Xdebug configuration needs no changes — port already defaults to 9003
• stopOnEntry is flagged the same way PhpStorm's "Break at first line" is, since every request now arrives
• pathMappings is written server path first, which is the easy thing to reverse
• skipFiles defaults to **/vendor/**, so stepping skips dependencies out of the box — the first thing to check when a step seems to skip something
• the extension's log option prints the protocol conversation to the Debug Console, the editor-side equivalent of our log level 5; Troubleshooting pairs it with our own log
• logpoints get a mention under breakpoints

maxConnections was checked and left out: it defaults to 0, meaning unlimited, so our always-on default creates no problem there.

Also corrects the same paragraph on the PhpStorm page: path mapping is needed whenever the reported paths differ from local ones — a container is the common case, not the only one.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-13 19:17 UTC