{"version":"2.1.233","anchor":"startup-notifications-rebuilt-as-a-declarative-registry","canonical_anchor":"startup-notifications-rebuilt-as-a-declarative-registry","heading":"Startup notifications rebuilt as a declarative registry","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/startup-notifications-rebuilt-as-a-declarative-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Startup notifications rebuilt as a declarative registry\n\nA dozen startup notices became one declarative registry; every message reads the same.\n\n**What**\n\nMore than a dozen startup notices are no longer separate React hooks. Each is now a descriptor with an id, a dependency function and a setup function, collected into one array and run by a single driver that re-runs a descriptor only when its dependencies change, cleaning up first. All the messages you see are unchanged.\n\n**Details**\n\n- Covers advisor consent and experimental banner, auto-mode-unavailable, chrome extension check, compliance taint, monitoring notice, model deprecation warning, the three fast-mode notices, IDE disconnected and install error, install issues, LSP initialization and teammate lifecycle.\n\n**Evidence**\n\n`id: \"lsp-initialization\"`\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}