{"version":"2.1.227","anchor":"storage-keys-are-now-validated-with-per-area-rules-and-reada","canonical_anchor":"storage-keys-are-now-validated-with-per-area-rules-and-reada","heading":"Storage keys are now validated with per-area rules and readable errors","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/storage-keys-are-now-validated-with-per-area-rules-and-reada","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Storage keys are now validated with per-area rules and readable errors\n\nStorage keys are checked before use, so malformed ones fail with a clear message.\n\n**What**\n\nA new layer checks every storage key before it reaches the storage engine and rejects malformed ones with a specific message instead of letting them through. You would only ever see one of these if something were already wrong.\n\n**Details**\n\n- It enumerates the legal directory names under the user config directory, including `mcp-discovery-cache`, and the plugin registry files: `installed`, `marketplaces`, `flagged`, `catalog`, `inUseSweep`.\n- Log channels are restricted, with the error text \"must be debug, telemetry or apiDump\".\n- Relationships are enforced too, such as a scratch relative path requiring a session id.\n\n**Evidence**\n\n`must be debug, telemetry or apiDump`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}