Support breakpoints in virtual source documents such as AL .dal files

[Fekete Gábor (feketegabor)]

Summary

• preserve virtual-document URIs when adding, removing, or logging breakpoints
• add an optional workingDirectory routing hint for virtual sources in multi-window sessions
• keep native POSIX and Windows file-path behavior unchanged
• document AL .dal breakpoint support and add focused routing/source URI tests

Why

DebugMCP previously passed every source argument to vscode.Uri.file(). That rewrites an AL virtual source such as al-preview://AlLang/.../Customer%20List.dal into a local file:// URI, so the Microsoft AL extension cannot resolve the document and the breakpoint cannot bind.

The new source URI helper preserves URI schemes while still treating Windows drive paths as files. The router can use workingDirectory to select the owning editor window; it can also reuse the active target or the sole registered window.

Validation

• npm run check-types
• npm run lint
• npm run bundle
• full extension-host test suite: 160 passing in Antigravity IDE 1.107.0
• integration test loaded the installed Microsoft AL extension and resolved the real Base Application Customer.dal virtual source
• end-to-end Business Central Cloud debug in Antigravity with AL extension 18.0.2668733:
  • added a breakpoint to al-preview://AlLang/437dbf0e84ff417a965ded2bb9650972/Page/22/Customer%20List.dal:1675
  • debugger stopped in standard Page 22 OnOpenPage
  • listed globals and locals, including Rec as Table Customer (18)
  • stepped from line 1675 to 1676, then continued and stopped the session
  • removed all test breakpoints

[Fekete Gábor (feketegabor)]

@microsoft-github-policy-service agree company="EcoBit Consulting Kft."