It stops reporting success over a missing part

The check that said done now says what it means

When the code on your Brain changes, it restarts its own services so the new code actually runs. That check counted a service which is not installed as a success — so on a machine where one was missing, it reported that everything had refreshed, wrote the version down, and never tried again. A missing service is now treated as what it is: a fault. It is reported, and it is deliberately not recorded as done, so the next start tries again rather than settling into a lie. The same family of fault had your Brain reading “up to date” as though it were one behind.

It puts the missing service back

Noticing is only half of it. When a service the Brain needs is not there, it now asks for it to be installed and starts it — one attempt per start, so a repair can never loop. If your gateway has ever shown as stopped for no visible reason, or an update seemed to do nothing at all, this is that.

Settings tells you what failed, in plain words

The reason a service failed was worked out and written down, and then only ever shown in a terminal. Settings said “Stopped — startup_failed”, which tells you something is wrong and nothing about what. The Gateway row now says what actually failed — and when the service has simply never been set up on that computer, it says that instead, because that is the truth.