GeezerVison

Hi @hxrshxz Thank you so much for this work!

A few things:

• Rather than communicating over JSON and writing a custom writer and parser, lets use the build-in communication in the Debug connection
• The debug connection is active even when the debugger is not connected in Java mode, so this is not limited to running a sketch with the Debugger active
• Rather than adding a whole new screen, let's just add it to the clipboard content that already exists when you click the version number

Hi @benfry, thank you for the feedback. I've updated the PR to address your points:

1. Direct JDWP Access: Switched to reading PApplet fields directly via JDI, removing the need for JSON or custom protocols.
2. Universal Diagnostics: Implemented a static Debugger.getDiagnostics(Runner) that works for both Run and Debug modes without requiring an active debug session.
3. Clipboard Integration: Simply appends sketch diagnostics to the existing version-click clipboard action. No new UI elements were added.

really sorry for taking so lonng

Hey @Stefterv can you please have a look when you are free , thanks for your time

Looks good @hxrshxz! Thank you!

Optionally, I think it would be good to add the same functionality to the new settings screen as the Generate Report button is much easier to find.
Also I think me and @catilac would need to think what kind of debug information would be helpful (renderer for example)
But neither are blockers for this PR so that can also be separate issues.