{"version":"2.1.247","anchor":"missing-user-settings-file-is-now-seeded-rather-than-skipped","canonical_anchor":"missing-user-settings-file-is-now-seeded-rather-than-skipped","heading":"Missing user settings file is now seeded rather than skipped","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/missing-user-settings-file-is-now-seeded-rather-than-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Missing user settings file is now seeded rather than skipped\n\nA missing user settings file is recorded as empty instead of causing a fallback read.\n\n**What**\n\nWhen the settings store reports no user settings file, the primer records an empty parse instead of leaving the entry unset, so later reads do not fall back to reading the file directly.\n\n**Details**\n\n- Logging now separates an absent file from an oversize or failing one; only the latter is described as served by the raw path.\n- The freshness watcher returns early under a new guard.\n\n**Evidence**\n\n`settingsPrime: user settings absent; seeded as none`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}