Your global config can now be read through the storage layer at startup, with a fallback to the plain file.
What's wrong with this entry?
The global config read at startup can go through the storage layer, honouring the recorded version and file stats and subscribing for updates, and falls back to reading the file directly with a warning if that fails.
- Only used when the newer storage backend is pinned on.
- Detecting a credentials change now asks the backend for a credentials version rather than stat'ing
.credentials.json.
Startup config read through storage failed; reading the file directly:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.