{"version":"2.1.224","anchor":"pdf-page-extraction-and-several-caches-read-through-the-stor","canonical_anchor":"pdf-page-extraction-and-several-caches-read-through-the-stor","heading":"PDF page extraction and several caches read through the storage layer","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/pdf-page-extraction-and-several-caches-read-through-the-stor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### PDF page extraction and several caches read through the storage layer\n\nPDF page images and several caches now read through a shared storage layer instead of raw files.\n\n**What**\n\nExtracted PDF page images are now listed and read back through the shared storage abstraction rather than direct filesystem calls, with a guard that fails if the extraction directory sits outside the session's tool-results store. Model-capability caches and the closed-issues cache gained the same storage-backed paths; all of them fall back to the previous filesystem path when no storage handle is supplied.\n\n**Evidence**\n\n`PDF extraction directory is outside the session tool-results store`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}