What you write is correct, when the core reflashes itself, the cloud is in the ‘dark’ about the cores activities. When you flash a core the blue dot stays breathing blue. Why not make it pulse, slower than on the core, purple, until the core establishes a connection again, and than switch to breathing blue again.
Speed and synchronicity are less important than feedback.
I did not explore the cloud part of the software jet. So the next idea might not be possible, or a bit silly, but I give it a go. Why don’t we create a global variable that can be altered by the application to reflect the application’s status. During IDE activity the value of this var will be transmitted to the cloud and relayed to the IDE. And let’s give it an update rate of say, 10 seconds. This var can be used for status information on the IDE side while developing.
I know the IDE has less priority at this time, but the visual feedback during flashing will be highly appreciated.