{"version":"2.1.248","anchor":"plan-file-cache-distinguishes-known-absent-from-unknown","canonical_anchor":"plan-file-cache-distinguishes-known-absent-from-unknown","heading":"Plan file cache distinguishes \"known absent\" from \"unknown\"","tier":"internal","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plan-file-cache-distinguishes-known-absent-from-unknown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plan file cache distinguishes \"known absent\" from \"unknown\"\n\nPlan file lookups remember when a file is genuinely absent, so recovery after resume keeps more.\n\n**What**\n\nPlan and workshop file lookups no longer just check whether a key is present; they tell a cached \"this file does not exist\" apart from never having looked, wait for a settle step before reading, and recovery after resume or fork stores what it recovered instead of always throwing the entry away.\n\n**Evidence**\n\n`Workshop doc recovered from file snapshot, `\n\n- Area: Plan Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}