{"version":"2.1.248","anchor":"plan-file-cache-stays-coherent-across-resume-fork-and-recove","canonical_anchor":"plan-file-cache-stays-coherent-across-resume-fork-and-recove","heading":"Plan file cache stays coherent across resume, fork and recovery","tier":"notice","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plan-file-cache-stays-coherent-across-resume-fork-and-recove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plan file cache stays coherent across resume, fork and recovery\n\nResume, fork and recovery keep the plan file cache warm instead of racing to rebuild it.\n\n**What**\n\nResume, fork and recovery paths now write the content they just produced back into the plan file cache rather than invalidating it, via new settle, observe and watch helpers, and resume priming is tracked as a single in-flight promise so concurrent callers wait on one pass instead of racing.\n\n**Details**\n\n- Sits behind the same in-module condition that already guarded the plan file cache; what that condition reads is not visible from the cache code itself.\n\n**Evidence**\n\n`settlePlanFile`\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}