{"version":"2.1.239","anchor":"user-settings-can-be-seeded-from-the-storage-backend-before-","canonical_anchor":"user-settings-can-be-seeded-from-the-storage-backend-before-","heading":"User settings can be seeded from the storage backend before the first file read","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/user-settings-can-be-seeded-from-the-storage-backend-before-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### User settings can be seeded from the storage backend before the first file read\n\nSettings can be pre-loaded from the storage backend before the settings file is read from disk.\n\n**What**\n\nAt 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.\n\n**Details**\n\n- The running seeder's backend logic was moved into the same shared helper.\n- Which internal flag pins the backend-settings mode is not identified in the build.\n\n**Evidence**\n\n`settingsPrime: user settings already read before start-up; seed skipped`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}