{"version":"2.1.232","anchor":"saved-prompt-cache-diagnostics-are-bounds-checked-when-loade","canonical_anchor":"saved-prompt-cache-diagnostics-are-bounds-checked-when-loade","heading":"Saved prompt-cache diagnostics are bounds-checked when loaded","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/saved-prompt-cache-diagnostics-are-bounds-checked-when-loade","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Saved prompt-cache diagnostics are bounds-checked when loaded\n\nSaved prompt-cache diagnostics are size-checked on load so a corrupt file is rejected.\n\n**What**\n\nThe stored per-source prompt-cache diagnosis data is now validated on load with hard size limits, so a corrupted or oversized file is rejected instead of being loaded wholesale.\n\n**Details**\n\n- Strings are capped at 200 characters, tool-name and per-tool hash maps at 2000 entries, block hash arrays at 5000, and message hashes at 20000.\n- The `globalCacheStrategy` field is checked against a fixed set of accepted values, one of which is `tool_based`.\n- Clearing is now selective: a subset of sources can be invalidated rather than wiping the entire map.\n\n**Evidence**\n\n`tool_based`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}