Forward VS Code debug output to dashboard logs, apphost errors show in Aspire debug session console

[adamint]

Description

Forward non-telemetry VS Code debug adapter output events to DCP service logs so output shown in the VS Code Debug Console also appears in Aspire Dashboard console logs.

This fixes JavaScript resource logs by launching Node resources through VS Code js-debug's pwa-node adapter with outputCapture: "std", which is required for package-manager and Vite stdout/stderr to be emitted as Debug Adapter Protocol output events. The tracker forwards those output events to DCP as serviceLogs.

This also incorporates and supersedes the AppHost startup failure reporting from #16516. This is because pwa-node tracking would also be required to get ts AppHost stderr. AppHost failures that happen before the child debug session starts now write details to the Debug Console as stderr instead of only showing a dialog. Build failures whose output was already streamed are not replayed a second time, and AppHost child debug output is mirrored back to the parent Aspire Debug Console so TypeScript AppHost runtime/startup errors are visible in the same place as C# AppHost errors.

Fixes #16468
Fixes #15578

Validation:

• npm run compile-tests
• npm run unit-test -- --grep "Node Debugger Tests|Debug Adapter Tracker Tests|failed AppHost start"

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire.dev issue:
      • New issue
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16512

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16512"

[Copilot]

Pull request overview

This PR improves the VS Code extension’s debug integration by forwarding non-telemetry Debug Adapter Protocol (DAP) output events to the DCP service logs, so that Node/Vite output visible in the VS Code Debug Console also appears in the Aspire Dashboard logs for JavaScript resources launched under VS Code debugging.

Changes:

• Forward all non-telemetry DAP output events (not just stdout/stderr) to DCP as serviceLogs.
• Add unit coverage validating that non-telemetry categories are forwarded and telemetry output is ignored.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
extension/src/debugger/adapterTracker.ts	Broadened forwarding logic to send non-telemetry debug adapter output events as DCP serviceLogs.
extension/src/test/adapterTracker.test.ts	Added tests ensuring non-telemetry output events are forwarded (with correct stderr mapping) and telemetry output is excluded.

[adamint]

I confirmed the following 4 cases work:

• c# OR ts apphost w/build error shows that build error in the aspire debug session
• c# OR ts apphost w/node apps have console logs appear in the aspire dashboard