@contractspec/bundle.library 3.9.8 → 3.9.9

package/dist/node/components/docs/libraries/LibrariesApplicationShellPage.content.js

@@ -1,11 +1,12 @@
-var n=Object.defineProperty;var o=(e)=>e;function i(e,t){this[e]=o.bind(null,t)}var s=(e,t)=>{for(var a in t)n(e,a,{get:t[a],enumerable:!0,configurable:!0,set:i.bind(t,a)})};var r=(e,t)=>()=>(e&&(t=e(e=0)),t);var c=`import {
+var i=Object.defineProperty;var n=(e)=>e;function o(e,t){this[e]=n.bind(null,t)}var s=(e,t)=>{for(var a in t)i(e,a,{get:t[a],enumerable:!0,configurable:!0,set:o.bind(t,a)})};var r=(e,t)=>()=>(e&&(t=e(e=0)),t);var l=`import {
   AppShell,
-  PageOutline,
-  type AppShellNavigationSection,
+  type ShellCommandGroup,
+  type ShellNavSection,
+  type ShellNotificationCenter,
   type PageOutlineItem,
 } from "@contractspec/lib.design-system/shell";
 
-const navigation: AppShellNavigationSection[] = [
+const navigation: ShellNavSection[] = [
   {
     title: "Workspace",
     items: [
@@ -22,6 +23,16 @@ const navigation: AppShellNavigationSection[] = [
   },
 ];
 
+const commands: ShellCommandGroup[] = [
+  {
+    heading: "Quick actions",
+    items: [
+      { id: "new-contract", label: "New contract", shortcut: "N" },
+      { id: "import", label: "Import existing app" },
+    ],
+  },
+];
+
 const outline: PageOutlineItem[] = [
   {
     id: "architecture",
@@ -34,41 +45,104 @@ const outline: PageOutlineItem[] = [
   },
 ];
 
+const notifications: ShellNotificationCenter = {
+  label: "Notifications",
+  loading: false,
+  unreadCount: 2,
+  items: [
+    {
+      id: "contract-approved",
+      title: "Contract approved",
+      body: "Billing.create is ready to publish.",
+      status: "unread",
+      createdAt: "2026-04-29T09:30:00Z",
+      actionUrl: "/contracts/billing.create",
+      category: "Review",
+    },
+  ],
+  onSelect: (item) => openNotificationTarget(item),
+  onMarkRead: (item) => markNotificationRead(item.id),
+  onMarkAllRead: () => markAllNotificationsRead(),
+};
+
 export function WorkspacePage() {
   return (
     <AppShell
-      brand={{ label: "ContractSpec", href: "/dashboard" }}
+      title="ContractSpec"
+      homeHref="/dashboard"
       navigation={navigation}
+      commands={commands}
       breadcrumbs={[
         { label: "Workspace", href: "/dashboard" },
         { label: "Contracts" },
       ]}
-      command={{
-        placeholder: "Search contracts or run an action",
-        groups: [
-          {
-            title: "Quick actions",
-            actions: [
-              { id: "new-contract", label: "New contract" },
-              { id: "import", label: "Import existing app" },
-            ],
-          },
-        ],
-      }}
-      user={{
-        name: "Ada Lovelace",
-        email: "ada@example.com",
-        actions: [{ label: "Sign out", onSelect: () => signOut() }],
-      }}
-      pageOutline={<PageOutline items={outline} activeId="desktop" />}
+      notifications={notifications}
+      pageOutline={outline}
+      activeHref="/contracts"
+      activeOutlineId="desktop"
+      userMenu={<UserMenu onSignOut={() => signOut()} />}
     >
       <main>{/* route content */}</main>
     </AppShell>
   );
-}`,d=`You are implementing a modern application shell from scratch.
+}`,d=`import {
+  ListNotificationsOutputModel,
+  MarkNotificationReadInputModel,
+} from "@contractspec/lib.contracts-spec/notifications";
+import {
+  notificationsSchemaContribution,
+  renderNotificationTemplate,
+} from "@contractspec/lib.notification";
+import type { ShellNotificationCenter } from "@contractspec/lib.design-system/shell";
+
+type NotificationListResult = {
+  unreadCount: number;
+  notifications: Array<{
+    id: string;
+    title: string;
+    body: string;
+    type: string;
+    status: string;
+    readAt?: string | Date | null;
+    createdAt: string | Date;
+    actionUrl?: string;
+    metadata?: Record<string, unknown>;
+  }>;
+};
+
+export function toShellNotifications(
+  data: NotificationListResult,
+  actions: {
+    open: (id: string) => void;
+    markRead: (input: { notificationId: string }) => void;
+    markAllRead: () => void;
+  }
+): ShellNotificationCenter {
+  return {
+    unreadCount: data.unreadCount,
+    items: data.notifications.map((notification) => ({
+      id: notification.id,
+      title: notification.title,
+      body: notification.body,
+      status: notification.status,
+      createdAt: notification.createdAt,
+      actionUrl: notification.actionUrl,
+      category: notification.type,
+      metadata: notification.metadata,
+    })),
+    onSelect: (item) => actions.open(item.id),
+    onMarkRead: (item) => actions.markRead({ notificationId: item.id }),
+    onMarkAllRead: actions.markAllRead,
+  };
+}
+
+void ListNotificationsOutputModel;
+void MarkNotificationReadInputModel;
+void notificationsSchemaContribution;
+void renderNotificationTemplate;`,p=`You are implementing a modern application shell from scratch.
 
 Goal:
-Build a reusable application shell for a React/Next.js web app and an Expo React Native app. The shell must provide a desktop sidebar, desktop topbar, command search, breadcrumbs, nested navigation, user/auth actions, and an in-page section navigator called PageOutline.
+Build a reusable application shell for a React/Next.js web app and an Expo React Native app. The shell must provide a desktop sidebar, desktop topbar, command search, breadcrumbs, nested navigation, user/auth actions, in-app notifications, and an in-page section navigator called PageOutline.
 
 Use this architecture:
 - Keep route content independent from navigation chrome.
@@ -76,29 +150,37 @@ Use this architecture:
 - Create a command model with search input, grouped suggestions, quick actions, keyboard shortcut labels, empty state, and loading state.
 - Create a breadcrumb model for the topbar.
 - Create a PageOutline model for right-side in-page navigation with exactly three supported levels. It should render anchors, support active section state, and degrade gracefully when no sections exist.
+- Create a ShellNotificationCenter model with render-ready items, unread count, loading and empty states, onSelect, onMarkRead, onMarkAllRead, and optional custom item rendering.
 - Expose the system from the design system or a dedicated shell module, not from a single app route.
 
+Notification boundary:
+- Use @contractspec/lib.contracts-spec/notifications as the canonical source for notification contracts, operation models, and feature metadata.
+- Use @contractspec/lib.notification for reusable notification entities, schema contribution, channels, templates, and i18n helpers.
+- Keep persistence, polling/subscriptions, delivery providers, and optimistic mutations in the host application or notification runtime layer.
+- Pass only render-ready ShellNotificationCenter state into AppShell so the design system does not import or own notification runtime behavior.
+
 Desktop behavior:
 - Persistent left sidebar with app logo/title, command trigger, grouped navigation, nested submenus, and current user/auth/logout area.
 - Topbar with breadcrumbs and an optional command trigger.
+- Topbar notification trigger with unread badge, loading/empty states, mark-read actions, and item selection.
 - Content area with optional right PageOutline.
 - Keep dimensions stable. Navigation labels must not resize layout on hover or active state.
 
 Mobile web behavior:
 - Use bottom navigation for the primary destinations.
-- Put deeper navigation, command search, auth actions, and secondary actions behind a menu or drawer.
+- Put deeper navigation, command search, notifications, auth actions, and secondary actions behind a menu or drawer when the topbar cannot safely hold them.
 - Keep route content first and make the shell controls reachable without covering important content.
 
 Native behavior:
 - Add .native.tsx entrypoints for Expo/React Native.
-- Prefer bottom tabs for primary destinations and a menu/sheet for deeper navigation and account actions.
-- Keep the same typed navigation, command, breadcrumb, and PageOutline data contracts across web and native.
+- Prefer bottom tabs for primary destinations and a menu/sheet for deeper navigation, notifications, and account actions.
+- Keep the same typed navigation, command, breadcrumb, notification, and PageOutline data contracts across web and native.
 
 Implementation constraints:
 - Reuse the existing design-system primitives, tokens, icons, and accessibility patterns.
 - Do not hardcode app-specific routes in the shell component.
 - Do not introduce a new dependency unless the repo already uses it for dialogs, menus, icons, or navigation.
-- Include tests for navigation rendering, nested items, command filtering, breadcrumbs, PageOutline level handling, active section state, and mobile/native adaptation contracts.
+- Include tests for navigation rendering, nested items, command filtering, breadcrumbs, notification unread badge/loading/empty/callback behavior, PageOutline level handling, active section state, and mobile/native adaptation contracts.
 - Update docs and exports so developers can import the shell from a stable public API.
 
 Deliverables:
@@ -106,15 +188,18 @@ Deliverables:
 - Web shell components.
 - Native shell components or adapters.
 - PageOutline component with three-level support.
+- ShellNotifications or equivalent notification center component for web and native shell placement.
 - Usage example.
-- Focused tests and typecheck/build evidence.`,p=`You are refactoring an existing application to use the shared application shell system.
+- Focused tests and typecheck/build evidence.`,m=`You are refactoring an existing application to use the shared application shell system.
 
 Goal:
-Replace app-specific sidebar, topbar, breadcrumb, command palette, account menu, mobile navigation, and in-page table-of-contents code with the shared AppShell and PageOutline system.
+Replace app-specific sidebar, topbar, breadcrumb, command palette, notification badge/inbox, account menu, mobile navigation, and in-page table-of-contents code with the shared AppShell, ShellNotifications, and PageOutline system.
 
 Start by auditing:
 - Current layout wrappers and route groups.
 - Sidebar, topbar, breadcrumb, command/search, auth menu, and mobile navigation implementations.
+- Existing notification badges, inbox panels, toasts that represent durable in-app items, unread count queries, mark-read actions, and delivery modules.
+- Imports from @contractspec/module.notifications that should migrate to @contractspec/lib.contracts-spec/notifications or @contractspec/lib.notification.
 - Any duplicated navigation arrays, route labels, icon maps, access-control checks, and active-state logic.
 - Any in-page summary/table-of-contents components that should become PageOutline data.
 - Web-only assumptions that would block Expo/React Native adaptation.
@@ -123,25 +208,28 @@ Refactor plan:
 1. Define a single typed navigation source for primary nav, grouped sidebar nav, nested children, labels, icons, badges, disabled states, and permissions.
 2. Map existing command/search behavior into grouped command actions with search text and quick actions.
 3. Map existing route metadata into breadcrumbs.
-4. Convert page table-of-contents or section summary data into PageOutline items with a maximum of three levels.
-5. Wrap app routes in AppShell while keeping page content components route-local.
-6. Move primary mobile destinations into bottom navigation and deeper/account actions into a menu or drawer.
-7. Add or preserve .native.tsx adapters when the app targets Expo.
+4. Move canonical notification contracts to @contractspec/lib.contracts-spec/notifications and reusable helpers to @contractspec/lib.notification; keep the old module shim only for compatibility imports that still need the legacy module id.
+5. Convert notification query results into ShellNotificationCenter items with unreadCount, loading, empty state, onSelect, onMarkRead, and onMarkAllRead callbacks.
+6. Convert page table-of-contents or section summary data into PageOutline items with a maximum of three levels.
+7. Wrap app routes in AppShell while keeping page content components route-local.
+8. Move primary mobile destinations into bottom navigation and deeper/account/notification actions into a menu or drawer.
+9. Add or preserve .native.tsx adapters when the app targets Expo.
 
 Preserve behavior:
 - Existing route URLs and access rules.
 - Existing keyboard shortcuts where they are public behavior.
 - Existing analytics or telemetry events on navigation and command actions.
+- Existing notification delivery semantics, unread count semantics, deep links, and mark-read behavior.
 - Existing auth/logout behavior.
 - Existing responsive breakpoints unless there is a documented design-system breakpoint to adopt.
 
 Quality gates:
 - Add regression tests around current visible navigation before removing old shell code when coverage is missing.
-- Test active nav state, nested nav expansion, command search/action invocation, breadcrumbs, auth menu, mobile bottom navigation, and PageOutline anchor behavior.
+- Test active nav state, nested nav expansion, command search/action invocation, breadcrumbs, notification unread badge/loading/empty/callback behavior, auth menu, mobile bottom navigation, and PageOutline anchor behavior.
 - Run lint, typecheck, and the app's relevant test/build command.
 - Remove dead app-specific shell components only after the shared shell path is verified.
 
 Output:
 - List old shell files removed or simplified.
 - List new shared shell integration points.
-- Include before/after route coverage and verification commands.`,m=[{title:"Sidebar",body:"Desktop owns brand, command entry, grouped navigation, nested items, and account actions in one persistent scanning area."},{title:"Topbar",body:"Breadcrumbs stay visible while the current route changes. The command trigger can live here when the sidebar is collapsed or hidden."},{title:"PageOutline",body:"The right-side in-page navigator replaces ad hoc tables of contents. It supports three levels of section anchors and active state."},{title:"Mobile adapters",body:"Small web and native surfaces move primary destinations to bottom navigation and reserve drawers or menus for deep navigation and account actions."}];export{c as shellUsageExample,m as shellParts,d as scratchPrompt,p as refactorPrompt};
+- Include before/after route coverage and verification commands.`,u=[{title:"Contracts stay canonical",body:"Use @contractspec/lib.contracts-spec/notifications for operation models, feature metadata, and contract-level compatibility."},{title:"Runtime helpers stay reusable",body:"Use @contractspec/lib.notification for schema contribution, channel adapters, templates, and i18n without importing the deprecated module shim in new code."},{title:"Apps own live state",body:"Fetch, subscribe, persist, mutate, and reconcile notification state in the host app or runtime layer where auth and tenancy are known."},{title:"Shell receives view state",body:"Pass AppShell a ShellNotificationCenter with render-ready items, counts, loading state, and callbacks; the design system only renders affordances."}],h=[{title:"Sidebar",body:"Desktop owns brand, command entry, grouped navigation, nested items, and account actions in one persistent scanning area."},{title:"Topbar",body:"Breadcrumbs stay visible while the current route changes. Command search and notification affordances can live here when the sidebar is collapsed or hidden."},{title:"PageOutline",body:"The right-side in-page navigator replaces ad hoc tables of contents. It supports three levels of section anchors and active state."},{title:"Notifications",body:"The shell renders unread badges, item lists, loading/empty states, mark-read actions, and deep-link selection from host-owned notification state."},{title:"Mobile adapters",body:"Small web and native surfaces move primary destinations to bottom navigation and reserve drawers or menus for deep navigation, notifications, and account actions."}];export{l as shellUsageExample,h as shellParts,p as scratchPrompt,m as refactorPrompt,u as notificationGuide,d as notificationCenterExample};

package/dist/node/components/docs/libraries/LibrariesApplicationShellPage.js

@@ -1,11 +1,12 @@
-var v=Object.defineProperty;var f=(t)=>t;function y(t,n){this[t]=f.bind(null,n)}var k=(t,n)=>{for(var s in n)v(t,s,{get:n[s],enumerable:!0,configurable:!0,set:y.bind(n,s)})};var N=(t,n)=>()=>(t&&(n=t(t=0)),n);var d=`import {
+var w=Object.defineProperty;var k=(t)=>t;function N(t,n){this[t]=k.bind(null,n)}var O=(t,n)=>{for(var d in n)w(t,d,{get:n[d],enumerable:!0,configurable:!0,set:N.bind(n,d)})};var C=(t,n)=>()=>(t&&(n=t(t=0)),n);var p=`import {
   AppShell,
-  PageOutline,
-  type AppShellNavigationSection,
+  type ShellCommandGroup,
+  type ShellNavSection,
+  type ShellNotificationCenter,
   type PageOutlineItem,
 } from "@contractspec/lib.design-system/shell";
 
-const navigation: AppShellNavigationSection[] = [
+const navigation: ShellNavSection[] = [
   {
     title: "Workspace",
     items: [
@@ -22,6 +23,16 @@ const navigation: AppShellNavigationSection[] = [
   },
 ];
 
+const commands: ShellCommandGroup[] = [
+  {
+    heading: "Quick actions",
+    items: [
+      { id: "new-contract", label: "New contract", shortcut: "N" },
+      { id: "import", label: "Import existing app" },
+    ],
+  },
+];
+
 const outline: PageOutlineItem[] = [
   {
     id: "architecture",
@@ -34,41 +45,104 @@ const outline: PageOutlineItem[] = [
   },
 ];
 
+const notifications: ShellNotificationCenter = {
+  label: "Notifications",
+  loading: false,
+  unreadCount: 2,
+  items: [
+    {
+      id: "contract-approved",
+      title: "Contract approved",
+      body: "Billing.create is ready to publish.",
+      status: "unread",
+      createdAt: "2026-04-29T09:30:00Z",
+      actionUrl: "/contracts/billing.create",
+      category: "Review",
+    },
+  ],
+  onSelect: (item) => openNotificationTarget(item),
+  onMarkRead: (item) => markNotificationRead(item.id),
+  onMarkAllRead: () => markAllNotificationsRead(),
+};
+
 export function WorkspacePage() {
   return (
     <AppShell
-      brand={{ label: "ContractSpec", href: "/dashboard" }}
+      title="ContractSpec"
+      homeHref="/dashboard"
       navigation={navigation}
+      commands={commands}
       breadcrumbs={[
         { label: "Workspace", href: "/dashboard" },
         { label: "Contracts" },
       ]}
-      command={{
-        placeholder: "Search contracts or run an action",
-        groups: [
-          {
-            title: "Quick actions",
-            actions: [
-              { id: "new-contract", label: "New contract" },
-              { id: "import", label: "Import existing app" },
-            ],
-          },
-        ],
-      }}
-      user={{
-        name: "Ada Lovelace",
-        email: "ada@example.com",
-        actions: [{ label: "Sign out", onSelect: () => signOut() }],
-      }}
-      pageOutline={<PageOutline items={outline} activeId="desktop" />}
+      notifications={notifications}
+      pageOutline={outline}
+      activeHref="/contracts"
+      activeOutlineId="desktop"
+      userMenu={<UserMenu onSignOut={() => signOut()} />}
     >
       <main>{/* route content */}</main>
     </AppShell>
   );
-}`,p=`You are implementing a modern application shell from scratch.
+}`,m=`import {
+  ListNotificationsOutputModel,
+  MarkNotificationReadInputModel,
+} from "@contractspec/lib.contracts-spec/notifications";
+import {
+  notificationsSchemaContribution,
+  renderNotificationTemplate,
+} from "@contractspec/lib.notification";
+import type { ShellNotificationCenter } from "@contractspec/lib.design-system/shell";
+
+type NotificationListResult = {
+  unreadCount: number;
+  notifications: Array<{
+    id: string;
+    title: string;
+    body: string;
+    type: string;
+    status: string;
+    readAt?: string | Date | null;
+    createdAt: string | Date;
+    actionUrl?: string;
+    metadata?: Record<string, unknown>;
+  }>;
+};
+
+export function toShellNotifications(
+  data: NotificationListResult,
+  actions: {
+    open: (id: string) => void;
+    markRead: (input: { notificationId: string }) => void;
+    markAllRead: () => void;
+  }
+): ShellNotificationCenter {
+  return {
+    unreadCount: data.unreadCount,
+    items: data.notifications.map((notification) => ({
+      id: notification.id,
+      title: notification.title,
+      body: notification.body,
+      status: notification.status,
+      createdAt: notification.createdAt,
+      actionUrl: notification.actionUrl,
+      category: notification.type,
+      metadata: notification.metadata,
+    })),
+    onSelect: (item) => actions.open(item.id),
+    onMarkRead: (item) => actions.markRead({ notificationId: item.id }),
+    onMarkAllRead: actions.markAllRead,
+  };
+}
+
+void ListNotificationsOutputModel;
+void MarkNotificationReadInputModel;
+void notificationsSchemaContribution;
+void renderNotificationTemplate;`,u=`You are implementing a modern application shell from scratch.
 
 Goal:
-Build a reusable application shell for a React/Next.js web app and an Expo React Native app. The shell must provide a desktop sidebar, desktop topbar, command search, breadcrumbs, nested navigation, user/auth actions, and an in-page section navigator called PageOutline.
+Build a reusable application shell for a React/Next.js web app and an Expo React Native app. The shell must provide a desktop sidebar, desktop topbar, command search, breadcrumbs, nested navigation, user/auth actions, in-app notifications, and an in-page section navigator called PageOutline.
 
 Use this architecture:
 - Keep route content independent from navigation chrome.
@@ -76,29 +150,37 @@ Use this architecture:
 - Create a command model with search input, grouped suggestions, quick actions, keyboard shortcut labels, empty state, and loading state.
 - Create a breadcrumb model for the topbar.
 - Create a PageOutline model for right-side in-page navigation with exactly three supported levels. It should render anchors, support active section state, and degrade gracefully when no sections exist.
+- Create a ShellNotificationCenter model with render-ready items, unread count, loading and empty states, onSelect, onMarkRead, onMarkAllRead, and optional custom item rendering.
 - Expose the system from the design system or a dedicated shell module, not from a single app route.
 
+Notification boundary:
+- Use @contractspec/lib.contracts-spec/notifications as the canonical source for notification contracts, operation models, and feature metadata.
+- Use @contractspec/lib.notification for reusable notification entities, schema contribution, channels, templates, and i18n helpers.
+- Keep persistence, polling/subscriptions, delivery providers, and optimistic mutations in the host application or notification runtime layer.
+- Pass only render-ready ShellNotificationCenter state into AppShell so the design system does not import or own notification runtime behavior.
+
 Desktop behavior:
 - Persistent left sidebar with app logo/title, command trigger, grouped navigation, nested submenus, and current user/auth/logout area.
 - Topbar with breadcrumbs and an optional command trigger.
+- Topbar notification trigger with unread badge, loading/empty states, mark-read actions, and item selection.
 - Content area with optional right PageOutline.
 - Keep dimensions stable. Navigation labels must not resize layout on hover or active state.
 
 Mobile web behavior:
 - Use bottom navigation for the primary destinations.
-- Put deeper navigation, command search, auth actions, and secondary actions behind a menu or drawer.
+- Put deeper navigation, command search, notifications, auth actions, and secondary actions behind a menu or drawer when the topbar cannot safely hold them.
 - Keep route content first and make the shell controls reachable without covering important content.
 
 Native behavior:
 - Add .native.tsx entrypoints for Expo/React Native.
-- Prefer bottom tabs for primary destinations and a menu/sheet for deeper navigation and account actions.
-- Keep the same typed navigation, command, breadcrumb, and PageOutline data contracts across web and native.
+- Prefer bottom tabs for primary destinations and a menu/sheet for deeper navigation, notifications, and account actions.
+- Keep the same typed navigation, command, breadcrumb, notification, and PageOutline data contracts across web and native.
 
 Implementation constraints:
 - Reuse the existing design-system primitives, tokens, icons, and accessibility patterns.
 - Do not hardcode app-specific routes in the shell component.
 - Do not introduce a new dependency unless the repo already uses it for dialogs, menus, icons, or navigation.
-- Include tests for navigation rendering, nested items, command filtering, breadcrumbs, PageOutline level handling, active section state, and mobile/native adaptation contracts.
+- Include tests for navigation rendering, nested items, command filtering, breadcrumbs, notification unread badge/loading/empty/callback behavior, PageOutline level handling, active section state, and mobile/native adaptation contracts.
 - Update docs and exports so developers can import the shell from a stable public API.
 
 Deliverables:
@@ -106,15 +188,18 @@ Deliverables:
 - Web shell components.
 - Native shell components or adapters.
 - PageOutline component with three-level support.
+- ShellNotifications or equivalent notification center component for web and native shell placement.
 - Usage example.
-- Focused tests and typecheck/build evidence.`,m=`You are refactoring an existing application to use the shared application shell system.
+- Focused tests and typecheck/build evidence.`,h=`You are refactoring an existing application to use the shared application shell system.
 
 Goal:
-Replace app-specific sidebar, topbar, breadcrumb, command palette, account menu, mobile navigation, and in-page table-of-contents code with the shared AppShell and PageOutline system.
+Replace app-specific sidebar, topbar, breadcrumb, command palette, notification badge/inbox, account menu, mobile navigation, and in-page table-of-contents code with the shared AppShell, ShellNotifications, and PageOutline system.
 
 Start by auditing:
 - Current layout wrappers and route groups.
 - Sidebar, topbar, breadcrumb, command/search, auth menu, and mobile navigation implementations.
+- Existing notification badges, inbox panels, toasts that represent durable in-app items, unread count queries, mark-read actions, and delivery modules.
+- Imports from @contractspec/module.notifications that should migrate to @contractspec/lib.contracts-spec/notifications or @contractspec/lib.notification.
 - Any duplicated navigation arrays, route labels, icon maps, access-control checks, and active-state logic.
 - Any in-page summary/table-of-contents components that should become PageOutline data.
 - Web-only assumptions that would block Expo/React Native adaptation.
@@ -123,25 +208,28 @@ Refactor plan:
 1. Define a single typed navigation source for primary nav, grouped sidebar nav, nested children, labels, icons, badges, disabled states, and permissions.
 2. Map existing command/search behavior into grouped command actions with search text and quick actions.
 3. Map existing route metadata into breadcrumbs.
-4. Convert page table-of-contents or section summary data into PageOutline items with a maximum of three levels.
-5. Wrap app routes in AppShell while keeping page content components route-local.
-6. Move primary mobile destinations into bottom navigation and deeper/account actions into a menu or drawer.
-7. Add or preserve .native.tsx adapters when the app targets Expo.
+4. Move canonical notification contracts to @contractspec/lib.contracts-spec/notifications and reusable helpers to @contractspec/lib.notification; keep the old module shim only for compatibility imports that still need the legacy module id.
+5. Convert notification query results into ShellNotificationCenter items with unreadCount, loading, empty state, onSelect, onMarkRead, and onMarkAllRead callbacks.
+6. Convert page table-of-contents or section summary data into PageOutline items with a maximum of three levels.
+7. Wrap app routes in AppShell while keeping page content components route-local.
+8. Move primary mobile destinations into bottom navigation and deeper/account/notification actions into a menu or drawer.
+9. Add or preserve .native.tsx adapters when the app targets Expo.
 
 Preserve behavior:
 - Existing route URLs and access rules.
 - Existing keyboard shortcuts where they are public behavior.
 - Existing analytics or telemetry events on navigation and command actions.
+- Existing notification delivery semantics, unread count semantics, deep links, and mark-read behavior.
 - Existing auth/logout behavior.
 - Existing responsive breakpoints unless there is a documented design-system breakpoint to adopt.
 
 Quality gates:
 - Add regression tests around current visible navigation before removing old shell code when coverage is missing.
-- Test active nav state, nested nav expansion, command search/action invocation, breadcrumbs, auth menu, mobile bottom navigation, and PageOutline anchor behavior.
+- Test active nav state, nested nav expansion, command search/action invocation, breadcrumbs, notification unread badge/loading/empty/callback behavior, auth menu, mobile bottom navigation, and PageOutline anchor behavior.
 - Run lint, typecheck, and the app's relevant test/build command.
 - Remove dead app-specific shell components only after the shared shell path is verified.
 
 Output:
 - List old shell files removed or simplified.
 - List new shared shell integration points.
-- Include before/after route coverage and verification commands.`,u=[{title:"Sidebar",body:"Desktop owns brand, command entry, grouped navigation, nested items, and account actions in one persistent scanning area."},{title:"Topbar",body:"Breadcrumbs stay visible while the current route changes. The command trigger can live here when the sidebar is collapsed or hidden."},{title:"PageOutline",body:"The right-side in-page navigator replaces ad hoc tables of contents. It supports three levels of section anchors and active state."},{title:"Mobile adapters",body:"Small web and native surfaces move primary destinations to bottom navigation and reserve drawers or menus for deep navigation and account actions."}];import{CodeBlock as l,InstallCommand as w}from"@contractspec/lib.design-system";import{Box as h,HStack as O,VStack as o}from"@contractspec/lib.design-system/layout";import{Code as c,H1 as A,H2 as i,H3 as P,P as r,Text as b}from"@contractspec/lib.design-system/typography";import g from"@contractspec/lib.ui-link";import{ChevronRight as E}from"lucide-react";import{jsx as e,jsxs as a}from"react/jsx-runtime";function K(){return a(o,{className:"space-y-8",children:[a(o,{className:"space-y-4",children:[e(A,{className:"font-bold text-4xl",children:"Application shell"}),a(r,{className:"text-lg text-muted-foreground",children:["A reusable navigation system for product apps: desktop sidebar, topbar breadcrumbs, command search, account actions, mobile adapters, and a Notion-style ",e(c,{children:"PageOutline"})," for page sections."]})]}),a(o,{className:"space-y-4",children:[e(i,{className:"font-bold text-2xl",children:"Installation"}),e(w,{package:"@contractspec/lib.design-system"})]}),a(o,{className:"space-y-4",children:[e(i,{className:"font-bold text-2xl",children:"What It Standardizes"}),e(h,{className:"grid gap-4 md:grid-cols-2",children:u.map((t)=>a(h,{className:"card-subtle p-4",children:[e(P,{className:"font-semibold",children:t.title}),e(r,{className:"mt-2 text-muted-foreground text-sm leading-7",children:t.body})]},t.title))})]}),a(o,{className:"space-y-4",children:[e(i,{className:"font-bold text-2xl",children:"Import Surface"}),e(r,{className:"text-muted-foreground",children:"The shell is exposed as a focused design-system subpath so apps can adopt navigation chrome without pulling unrelated documentation or marketing helpers."}),e(l,{language:"tsx",filename:"app-shell-example.tsx",code:d})]}),a(o,{className:"space-y-4",children:[e(i,{className:"font-bold text-2xl",children:"AI Prompt: Build From Scratch"}),e(r,{className:"text-muted-foreground",children:"Use this prompt when the app does not already have a shell or when the design-system package needs the reusable primitive first."}),e(l,{language:"markdown",filename:"implement-application-shell.md",code:p})]}),a(o,{className:"space-y-4",children:[e(i,{className:"font-bold text-2xl",children:"AI Prompt: Refactor An App"}),e(r,{className:"text-muted-foreground",children:"Use this prompt when an app already has custom navigation chrome and needs to migrate without breaking route behavior."}),e(l,{language:"markdown",filename:"refactor-to-application-shell.md",code:m})]}),a(o,{className:"card-subtle space-y-3 p-6",children:[e(i,{className:"font-bold text-2xl",children:"Naming"}),a(r,{className:"text-muted-foreground",children:["Use ",e(c,{children:"AppShell"})," for the whole navigation frame and"," ",e(c,{children:"PageOutline"})," for the in-page navigation helper. The latter is the product-app equivalent of a table of contents, but it is intentionally named for live page sections rather than static documentation."]})]}),a(O,{className:"flex flex-wrap items-center gap-3 pt-2",children:[e(g,{href:"/docs/libraries/cross-platform-ui",className:"btn-ghost",children:e(b,{children:"Cross-platform UI"})}),a(g,{href:"/docs/libraries/design-system",className:"btn-primary",children:[e(b,{children:"Design System"})," ",e(E,{size:16})]})]})]})}export{K as LibrariesApplicationShellPage};
+- Include before/after route coverage and verification commands.`,b=[{title:"Contracts stay canonical",body:"Use @contractspec/lib.contracts-spec/notifications for operation models, feature metadata, and contract-level compatibility."},{title:"Runtime helpers stay reusable",body:"Use @contractspec/lib.notification for schema contribution, channel adapters, templates, and i18n without importing the deprecated module shim in new code."},{title:"Apps own live state",body:"Fetch, subscribe, persist, mutate, and reconcile notification state in the host app or runtime layer where auth and tenancy are known."},{title:"Shell receives view state",body:"Pass AppShell a ShellNotificationCenter with render-ready items, counts, loading state, and callbacks; the design system only renders affordances."}],g=[{title:"Sidebar",body:"Desktop owns brand, command entry, grouped navigation, nested items, and account actions in one persistent scanning area."},{title:"Topbar",body:"Breadcrumbs stay visible while the current route changes. Command search and notification affordances can live here when the sidebar is collapsed or hidden."},{title:"PageOutline",body:"The right-side in-page navigator replaces ad hoc tables of contents. It supports three levels of section anchors and active state."},{title:"Notifications",body:"The shell renders unread badges, item lists, loading/empty states, mark-read actions, and deep-link selection from host-owned notification state."},{title:"Mobile adapters",body:"Small web and native surfaces move primary destinations to bottom navigation and reserve drawers or menus for deep navigation, notifications, and account actions."}];import{CodeBlock as c,InstallCommand as R}from"@contractspec/lib.design-system";import{Box as l,HStack as A,VStack as i}from"@contractspec/lib.design-system/layout";import{Code as o,H1 as S,H2 as s,H3 as f,P as r,Text as v}from"@contractspec/lib.design-system/typography";import y from"@contractspec/lib.ui-link";import{ChevronRight as M}from"lucide-react";import{jsx as e,jsxs as a}from"react/jsx-runtime";function K(){return a(i,{className:"space-y-8",children:[a(i,{className:"space-y-4",children:[e(S,{className:"font-bold text-4xl",children:"Application shell"}),a(r,{className:"text-lg text-muted-foreground",children:["A reusable navigation system for product apps: desktop sidebar, topbar breadcrumbs, command search, account actions, mobile adapters, and a Notion-style ",e(o,{children:"PageOutline"})," for page sections, with prop-driven in-app notifications for web and native shells."]})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"Installation"}),e(R,{package:"@contractspec/lib.design-system"})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"What It Standardizes"}),e(l,{className:"grid gap-4 md:grid-cols-2",children:g.map((t)=>a(l,{className:"card-subtle p-4",children:[e(f,{className:"font-semibold",children:t.title}),e(r,{className:"mt-2 text-muted-foreground text-sm leading-7",children:t.body})]},t.title))})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"Import Surface"}),e(r,{className:"text-muted-foreground",children:"The shell is exposed as a focused design-system subpath so apps can adopt navigation chrome without pulling unrelated documentation or marketing helpers."}),e(c,{language:"tsx",filename:"app-shell-example.tsx",code:p})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"Notification Center Boundary"}),a(r,{className:"text-muted-foreground",children:["Notifications are part of the shell experience, but the design system only renders the affordance. Contracts, runtime helpers, persistence, delivery, auth, and subscriptions stay outside the shell and feed a render-ready ",e(o,{children:"ShellNotificationCenter"})," into"," ",e(o,{children:"AppShell"}),"."]}),e(l,{className:"grid gap-4 md:grid-cols-2",children:b.map((t)=>a(l,{className:"card-subtle p-4",children:[e(f,{className:"font-semibold",children:t.title}),e(r,{className:"mt-2 text-muted-foreground text-sm leading-7",children:t.body})]},t.title))}),e(c,{language:"tsx",filename:"notification-center-boundary.ts",code:m})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"AI Prompt: Build From Scratch"}),e(r,{className:"text-muted-foreground",children:"Use this prompt when the app does not already have a shell, command surface, page outline, or in-app notification center."}),e(c,{language:"markdown",filename:"implement-application-shell.md",code:u})]}),a(i,{className:"space-y-4",children:[e(s,{className:"font-bold text-2xl",children:"AI Prompt: Refactor An App"}),e(r,{className:"text-muted-foreground",children:"Use this prompt when an app already has custom navigation chrome and notification UI that need to migrate without breaking route behavior, unread counts, or delivery semantics."}),e(c,{language:"markdown",filename:"refactor-to-application-shell.md",code:h})]}),a(i,{className:"card-subtle space-y-3 p-6",children:[e(s,{className:"font-bold text-2xl",children:"Naming"}),a(r,{className:"text-muted-foreground",children:["Use ",e(o,{children:"AppShell"})," for the whole navigation frame and"," ",e(o,{children:"PageOutline"})," for the in-page navigation helper. The latter is the product-app equivalent of a table of contents, but it is intentionally named for live page sections rather than static documentation. Use ",e(o,{children:"ShellNotifications"})," for the notification affordance when it is rendered directly, or pass the same data contract through ",e(o,{children:"AppShell"})," with the"," ",e(o,{children:"notifications"})," prop."]})]}),a(A,{className:"flex flex-wrap items-center gap-3 pt-2",children:[e(y,{href:"/docs/libraries/cross-platform-ui",className:"btn-ghost",children:e(v,{children:"Cross-platform UI"})}),a(y,{href:"/docs/libraries/design-system",className:"btn-primary",children:[e(v,{children:"Design System"})," ",e(M,{size:16})]})]})]})}export{K as LibrariesApplicationShellPage};