Protocol, compatibility, and build modes

Core and the extension exchange versioned diagnostic messages through the VM service. Compatible protocol major versions are required; compatible minor additions may introduce fields an older reader ignores.

Availability boundary

• the application must run on a supported non-product Dart VM with a VM service connection;
• the extension package belongs in application dev_dependencies;
• product VM builds and web builds do not expose the diagnostic bridge;
• opening the compiled extension through file:// bypasses its DevTools host and is unsupported.

No application initialization call is required. The bridge activates live payload work only after a compatible DevTools handshake and listener.

When the screen is empty

Check build mode, VM service target, core/extension compatibility, and whether a UseCase instance is currently alive. Malformed or incompatible isolate data is omitted rather than allowed to corrupt the complete overview.

The publishable package contains protocol models and compiled extension assets. Flutter source is maintained in the separate, non-published usecase_forge_devtools_extension workspace.