Bell icon notification badge resets after WebContainer cold start

StackBlitz surfaces TypeScript errors, build failures, and WebContainer process crashes through a bell icon in the activity bar. The notification system currently offers only a global enable/disable toggle without per-category severity filtering. A specific unresolved behavior is whether dismissed notifications retain their state across browser sessions or are cleared when the WebContainer runtime cold-starts. This affects workflow continuity when returning to a project after an idle period.

Given the sandboxed iframe architecture prevents third-party extensions from hooking into the notification system, and the dismissal persistence logic is not documented in the WebContainer release notes, the expected behavior remains ambiguous.

• Does the bell icon badge count persist across browser sessions when the WebContainer is warm?
• Is dismissal state tied to the WebContainer process lifecycle or to local storage?
• Are there any hidden settings or enterprise-tier controls that govern notification persistence?