MCP server claims that hot_reload succeeded when it actually failed

[athomas]

Gemini CLI used the MCP server to perform a hot_reload that seemed successful but the debug console contained output saying that the hot reload was rejected because of unsupported changes and that a hot restart is required.

 │ ✓  hot_reload (dart MCP Server) {}                                                                                                              │
 │                                                                                                                                                 │
 │    Hot reload succeeded.       

Ideally, Gemini CLI would have performed the hot restart (there's another issue to support that as a tool) in response to the rejected hot reload. At least, it should not claim the hot reload succeeded when it actually did not.

Note: this was a Flutter Web application.

[jakemac53]

We are using the success field from the service extension response - https://github.com/dart-lang/ai/blob/main/pkgs/dart_mcp_server/lib/src/mixins/dtd.dart#L401.

Sounds like that returns success even if the hot reload doesn't work.