Support source-mapped stack traces in list_console_messages

[wuzhiming]

Is your feature request related to a problem? Please describe.

When using list_console_messages to retrieve console errors, the returned stack traces do not reflect source-mapped locations, even if the JavaScript bundle includes valid sourcemaps and Chrome DevTools itself can resolve them.

This makes it difficult to debug production-bundled code or any code that relies on sourcemap mapping for readable stack traces. Currently the stack only shows the bundled/transpiled file and line numbers, which is far less informative.

Describe the solution you'd like

It would be helpful if list_console_messages could optionally return stack traces with sourcemap support, matching what DevTools shows in its console UI.

Describe alternatives you've considered

if not return it difficult to debug

Additional context

No response

[OrKoN]

We are already working on making it possible to re-use the DevTools frontend implementation via the MCP server. cc @natorion @szuend