fix(devtools): fix extension config name and VM service response parsing

[DrkXo]

• Update extension/devtools/config.yaml name to hyper_render_devtools to match package name and pass DevTools validation.
• Update devtools_ui _call to handle Map, String, or raw responses from VM service.
• Rebuild extension web assets in extension/devtools/build.

[vietnguyentuan2019]

Thank you @DrkXo — great catch, and a real one: the inspector had never been able to connect.

I verified both bugs against a live app:

• config.yaml name must be the package name, or devtools_extensions validate rejects the extension.
• vm_service already unwraps the JSON-RPC envelope, so result.json is the extension payload. None of the payloads has a result key, so _call always returned null.

I pushed one maintainer commit on top of yours:

• _call now simply returns result.json (the String/Map branches never ran).
• extension/devtools/build is a maintainer rebuild. We rebuild prebuilt web assets ourselves because they ship to pub.dev and can't be reviewed line by line — nothing personal.
• I also added a test that pins the config name to the package name.

Squash-merging with you as author. It will ship in the next hyper_render_devtools release with credit in the CHANGELOG. Thanks again! 🙏

[DrkXo]

Thank you! 🙏 really appreciate you taking the time to verify everything and clean this up.

I’m glad the issues were tracked down and fixed properly.

I’m currently working on a separate fork/branch for [Readaway], which needed a couple of core changes:

• fix(core): use line top and height for highlight bounding boxes
• fix(core): bridge inter-word gaps and preserve internal spaces in getBoxesForCharRange

I kept these changes separate for now since they were needed for my project. If you think they would be useful in hyper_render itself, I’d be happy to have them included in the original repository as well. Just let me know and I can get them over to you.

Thanks again for the review and for keeping the attribution/credit. Really appreciate it! 🙏

[vietnguyentuan2019]

Thanks a lot for the kind words, and for the fixes in this PR! 🙏

Yes please, those 2 fixes would be useful upstream. Could you open a separate PR from the latest main (it has 1.10.0 now)? Only these commits + the test file:

• 16b4c23 getBoxesForCharRange
• f5a313b bridge inter-word gaps
• 05e0245 line top/height

Please leave out the devtools build files, they will conflict with the DevTools v2 we just merged.

Few small things before merge:

• pass textScaler to the TextPainter, so highlight is not off when user changes system font size
• doc comment still says "tight height", but we use line height now
• add tests for white-space: pre and an inline image between 2 words (the 16px gap merge might join them)

Your authorship stays, of course. Thanks again!