Follow-up to #3071 (which closed #3014). That PR gave each spec NotificationTypeSchema member its own presentation, but no host mounted NotificationProvider — the capability existed and the console could not reach it. This wires it in.

What the console mounts now

inline is left out on purpose: rendering in place at the raiser is the whole difference between it and a banner, so a global inline outlet would collapse the two again. ConsoleShell's header documents the split so the next person doesn't "fix" it.

Two pieces worth reviewing

presentNotificationToast — the single place a notification becomes a sonner call, so the mapping is one testable function instead of a lambda in the shell:

• severity → sonner variant, in a Record<NotificationSeverityLevel, …> so a new spec severity fails type-check rather than silently rendering neutral;
• duration: 0 → Infinity. The contract's "persistent" passed through raw would make the toast vanish on the next tick;
• an absent duration is left undefined so ConsoleToaster's 4s default applies, rather than reinventing a number here;
• actions[0] → sonner's one action slot (a notification needing more belongs on a banner or an alert).

ConsoleNotificationBanners — NotificationBanners gated on useHasNotificationProvider(). ConsoleShell is deliberately a set of composable pieces a host assembles in its own App.tsx, so ConsoleLayout can legitimately render without the provider above it — and useNotifications() throws there, which would white-screen the whole app instead of simply showing no banners.

Both are exported for hand-assembled shells. The provider's defaultDuration matches ConsoleToaster's 4s, so a snackbar and a toast raised together disappear together.

Verification

In the running console (apps/console dev server, login route — which renders inside ConsoleShell): a toast, a snackbar with an Undo action, and a blocking alert dialog on screen at once, visibly distinct — the exact collapse #3014 was about, gone. Raising an inline with no outlet logs the dev warning naming the component to mount, and exactly once per notify() (measured, not assumed). No console errors on boot with the new root provider.

The banner placement is covered by tests rather than a screenshot: it lives in ConsoleLayout, which is behind auth, and standing up a backend for one strip was disproportionate — ConsoleShell.notifications.test.tsx renders ConsoleNotificationBanners inside the real ConsoleShell and asserts it lands on data-notification-surface="banner" while sonner is never called.

Suites:

• packages/app-shell: 2047 tests, 247 files, all green (includes the 15 new ones — 7 shell integration + 8 toast-mapping).
• tsc --noEmit clean on @object-ui/app-shell; eslint 0 errors on every touched file.

Docs: the notifications guide gains an "In the console" section, plus the @object-ui/app-shell README.

Refs #3014, #2942.

🤖 Generated with Claude Code