Settings can be pre-loaded from the storage backend before the settings file is read from disk.
What's wrong with this entry?
At start-up, user settings can be read from the storage backend and loaded into the settings store before the settings file is read from disk, logging whether it seeded, skipped because the file had already been read, or fell back. It runs only when the session pins settings to the backend; otherwise the ordinary file read serves, so behaviour is unchanged.
- The running seeder's backend logic was moved into the same shared helper.
- Which internal flag pins the backend-settings mode is not identified in the build.
settingsPrime: user settings already read before start-up; seed skipped
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.