[heswell]

Summary

The first piece of ui-portal-latest (#2657) split out for main. It brings the branch's @vuu-ui/vuu-notifications changes on their own, because nothing in them depends on @vuu-ui/core or any other portal change.

• Origins: NotificationOriginProvider tags notifications raised beneath it with an origin (moduleId, connectionId, and parentModuleId when nested). A notification that already has an origin keeps it. useNotificationOrigin reads the current one.
• Interceptor: NotificationsProvider takes an optional interceptor that returns "present" or "suppress" for each notification.
• One outermost provider: a NotificationsProvider inside another now renders only its children, so notifications from nested applications are shown once, by the outermost provider. On main providers are never nested (vuu-shell and individual showcase examples), so current behaviour is unchanged.
• Shared contexts: the contexts are kept on the global object, so module federation remotes that load their own copy of the package still find the host's provider.
• Callers outside a provider still have their notifications shown, by the most recently mounted provider, as on main. vuu-shell needs this: its WorkspaceProvider sits above the shell's NotificationsProvider.
• Additions: a record flag on notifications, and exports of the descriptor types and the isToastNotification/isWorkspaceNotification guards.

The package README now explains what this version adds, with a compatibility section and a section on what the Vuu server would need to add to make full use of these attributes in a portal.

Compatibility

The changes are backward compatible: exports and notification fields are only added, children is widened, and an app with one provider behaves as before. Two cases differ, and neither occurs on main outside showcase examples:

• Nested providers: the outermost now shows every notification. Before, the last one to mount did, usually the innermost.
• Sibling providers: each now shows its own notifications. Before, the last one to mount showed all of them.

The branch tested this with a Vitest DOM test. Here it's a Playwright component test instead, with three showcase examples under Notifications/NotificationOrigins.

Package versions and "type": "module" are left as they are on main; they belong to the later version bump.

Test plan

• npm run typecheck: clean
• vitest run: 1709 pass
• playwright test --project=components-chromium packages/vuu-notifications: 8 pass (4 existing, 4 new), including one for a caller outside the provider. It fails without the fallback.
• Biome clean on the changed files

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for papaya-valkyrie-395400 canceled.

Name	Link
🔨 Latest commit	880f057
🔍 Latest deploy log	https://app.netlify.com/projects/papaya-valkyrie-395400/deploys/6af0f62f0fe6620b8cf2f1f3