Not from the dev team but we already had some discussions 
If you link your âunansweredâ posts it might be easier for others to follow up on them reading this.
About the problem when a publish happens without Wifi/cloud there is an open issue milestoned for 0.4.9
https://github.com/spark/firmware/issues/761
It might not be desirable having to but defensive programming is one of the responsibilities of a programmer. So if there is no cloud/WiFi connection up and running (which can be checked) any attempt to use features relying on their availability might (should) be avoided.
The delayed reboot after flash in multithreaded mode is also known and looked into but do you actually need to reset manually since the device does definetly not reboot after a few seconds - as pointed out in the thread you are refering to.
@mdma from the dev team had posted once on that thread too - but granted, the follow up is still open
When you say you canât use AUTOMATIC anymore, what do you mean by that?
About the ever decreasing heap, have you got some code to look at? (Nevermind, if the code is posted in an other thread, if you just link to it)
Itâs not uncommon that the free heap shrinks at first as objects start their duty but this should sure stabilize.
But if you e.g. use String a lot, there is the risk of continously loosing heap as each instance at least allocates 16 byte (possibly more with longer contents) and frees it later on (once destroyed), but since there is no heap defragmentation implemented in firmware (at least that I know of), these fragments might not be usable for subsequent objects.