{"version":"2.1.280","anchor":"mass-delete-guard-check-across-multiple-memory-stores-no-co","canonical_anchor":"mass-delete-guard-check-across-multiple-memory-stores-no-co","heading":"Mass-delete guard check across multiple memory stores, no confirmed caller in my slice","tier":"internal","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mass-delete-guard-check-across-multiple-memory-stores-no-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Mass-delete guard check across multiple memory stores, no confirmed caller in my slice\n\nNew guard checks for mass-deletion across multiple memory stores at once, not yet confirmed to be in use\n\n**Unclear.** No confirmed caller for this function was found, so it's unclear when or whether it currently runs.\n\n**What**\n\nA new internal function checks a list of memory stores together, applying the same threshold used elsewhere to detect when too many files appear to have been deleted from a single store, but now across the whole set of stores at once. It reports back the threshold used, how many files are missing, and how many targets remain on disk.\n\n**Why**\n\nThis appears to be a safety check meant to catch large-scale accidental deletion spanning multiple memory stores, though it isn't confirmed where or when it is actually called.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}