Web Debug 0.12.0

Web Debug 0.12.0

Web Debug can now connect a browser action to its original source, executed code and request initiators. Safari console collection uses the official native MCP/Inspector transport and verifies actual delivery before accepting console checks.

• Set Chromium breakpoints in mapped original sources, inspect bounded source inventories, and opt into execution coverage and request diagnostics. Coverage stays off during fix verification.
• Compare captures and repair attempts with explanatory console, request, React and execution differences. These observations do not replace acceptance checks or establish causality.
• Capture real Safari console errors with source coordinates, drain observations between attempts, and preserve normal Safari browsing. Native input, CSS interactive maps and screenshot privacy guards remain covered.
• Preserve the 13-tool facade, selective schema-6 captures, direct-only WebMCP, registry recovery and the three plugin skills from 0.11.0.
• Keep diagnostic redaction valid for short private inputs, avoid blocked browser reads when JavaScript pauses, and update the MCP SDK to 1.32.1 with patched transitive dependencies.

Migration

Safari now requires Safari 27 or newer. webdriverEndpoint, --webdriver-endpoint, and the experimental BiDi transport are removed. Use browser: "safari" with remote automation enabled; WEB_DEBUG_SAFARIDRIVER_PATH can select another installed native driver. Runtime and console provenance are safari-mcp.

Safari remains visible and non-isolated. Chromium debugger/framework parity is unavailable, and network capture discloses Performance Resource Timing when native records are absent. Use either the plugin-bundled MCP connection or a standalone immutable 0.12.0 pin, avoiding duplicate registrations.

Verification

Verified with 228 tests, typecheck/build, zero production dependency audit findings, nine live browser/framework smokes and six comparison scenarios. The exact archive passed 13-tool/13-schema handshakes on Node 20, 22 and 24; a fresh public npm install passed too. Exact results and remaining platform limits are recorded in the release plan and compatibility evidence.