Complete deferred V8 Inspector browser, editor, and framework parity

[wieslawsoltes]

Follow-up to completed V8 Inspector milestone #7 and merged PR #8.

Deferred scope

The working debugger boundary is complete: secure discovery and attachment, Runtime/Debugger sessions, breakpoints, pause/step/resume, call stacks/scopes/watches, evaluation, source maps, live edit, profiling, heap tooling, WebAssembly debugging, bounded queues, production/diagnostic flavors, and shutdown hardening.

This backlog owns the concrete parity work deliberately deferred from that milestone:

• browser/renderer DevTools domains for DOM, CSS, layout highlighting, network/resource timing, storage, and event-listener/mutation breakpoints;
• advanced breakpoint/editor navigation UX and multi-target debugging;
• framework tooling, including React component, props, hooks, and state inspection;
• live-edit mutation conflict/history workflows;
• debugger accessibility and layout polish;
• explicit Chrome/IDE parity matrices and expanded release gates;
• rerunning the source-mapped 7GUIs React acceptance when a new Inspector-enabled V8 binary is published.

Boundary

This is deferred developer tooling. It is not part of the Code OSS native release acceptance graph under #227 and does not carry vscode-oss/planned.

Acceptance

• Each claimed domain or workflow has an explicit supported/unsupported matrix and real Chrome or compatible IDE evidence.
• Multi-target/session, disconnect, navigation, pause, backpressure, and shutdown behavior remain bounded and secure.
• Inspector-disabled production binaries retain the compiled-out behavior and performance guarantees established by Add V8 Inspector/CDP support for Chrome DevTools debugging #7/Add end-to-end WebScene V8 Inspector debugging #8.
• Cross-platform exact-head checks and refreshed source-mapped application evidence accompany each shipped parity stage.