{"version":"2.1.239","anchor":"message-list-warnings-and-the-permission-bell-join-the-per-h","canonical_anchor":"message-list-warnings-and-the-permission-bell-join-the-per-h","heading":"Message list warnings and the permission bell join the per-host registry","tier":"internal","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/message-list-warnings-and-the-permission-bell-join-the-per-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Message list warnings and the permission bell join the per-host registry\n\nMessage-list warnings and the permission bell also moved to the per-host tracking registry.\n\n**What**\n\nThe message list's one-time error reports and the permission-prompt bell debounce used module-level flags and timestamps; they now claim named keys on the per-host registry, so both are one-per-host rather than one-per-process.\n\n**Details**\n\n- The bell uses a variant that re-fires when the value changes, keyed on the dialog's id.\n\n**Evidence**\n\n`vml-keys-desync`\n\n- Area: Diagnostics\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}