@contractspec/bundle.library 3.9.6 → 3.9.8

package/src/components/docs/generated/docs-index.workspace-cli.json

@@ -1,10 +1,10 @@
 [
-	{
-		"id": "workspace-cli/workspace-cli",
-		"title": "workspace-cli",
-		"summary": "Core CLI operations for managing ContractSpec workspaces\n- **Type**: feature\n- **Version**: 1.0.0\n- **Stability**: stable\n- **Owners**: @lssm/core\n- **Tags**: cli, core\n- **File**: `packages/bundles/workspace/src/contracts/features/cli.feature.ts`",
-		"route": "/docs/reference/workspace-cli/workspace-cli",
-		"source": "generated",
-		"contentPath": "workspace-cli/workspace-cli.md"
-	}
-]
+  {
+    "id": "workspace-cli/workspace-cli",
+    "title": "workspace-cli",
+    "summary": "Core CLI operations for managing ContractSpec workspaces\n- **Type**: feature\n- **Version**: 1.0.0\n- **Stability**: stable\n- **Owners**: @lssm/core\n- **Tags**: cli, core\n- **File**: `packages/bundles/workspace/src/contracts/features/cli.feature.ts`",
+    "route": "/docs/reference/workspace-cli/workspace-cli",
+    "source": "generated",
+    "contentPath": "workspace-cli/workspace-cli.md"
+  }
+]

package/src/components/docs/getting-started/DataViewTutorialPage.tsx

@@ -45,8 +45,44 @@ export const TransactionHistory = defineDataView({
       { key: 'account', label: 'Account', dataPath: 'account', sortable: true },
       { key: 'owner', label: 'Owner', dataPath: 'owner', sortable: true },
       { key: 'status', label: 'Status', dataPath: 'status', sortable: true },
+      {
+        key: 'amount',
+        label: 'Amount',
+        dataPath: 'amount',
+        sortable: true,
+        format: { type: 'currency', currency: 'EUR', rounded: true },
+      },
+      {
+        key: 'renewalDate',
+        label: 'Renewal',
+        dataPath: 'renewalDate',
+        format: { type: 'date', dateStyle: 'medium' },
+      },
+      {
+        key: 'processingTime',
+        label: 'Processing time',
+        dataPath: 'processingMinutes',
+        format: { type: 'duration', unit: 'minute', display: 'digital' },
+      },
       { key: 'notes', label: 'Notes', dataPath: 'notes' },
     ],
+    filters: [
+      { key: 'status', label: 'Status', field: 'status', type: 'enum' },
+      {
+        key: 'amount',
+        label: 'Amount',
+        field: 'amount',
+        type: 'currency',
+        valueMode: 'range',
+      },
+      {
+        key: 'renewalDate',
+        label: 'Renewal',
+        field: 'renewalDate',
+        type: 'date',
+        valueMode: 'range',
+      },
+    ],
   },
 });`;
 
@@ -154,7 +190,10 @@ export function TransactionsPage() {
 						Column visibility, pinning, resizing, and row expansion stay
 						contract-driven
 					</li>
-					<li>Format rules (currency, dates, badges) applied consistently</li>
+					<li>
+						Typed format rules for numbers, percent values, currency, dates,
+						times, datetimes, and durations applied consistently
+					</li>
 					<li>Export to CSV/PDF using the same spec</li>
 					<li>A/B test different layouts without touching the backend</li>
 				</ul>

package/src/components/docs/guides/GuideContractDrivenFormsPage.content.ts

@@ -0,0 +1,98 @@
+export const leadCaptureFormCode = `import {
+  defineFormSpec,
+  FormRegistry,
+  responsiveFormColumns,
+} from "@contractspec/lib.contracts-spec/forms";
+import { fromZod } from "@contractspec/lib.schema";
+import { z } from "zod";
+
+const LeadCaptureModel = fromZod(
+  z.object({
+    fullName: z.string().min(1),
+    email: z.string().email(),
+    company: z.string().min(1),
+    intent: z.enum(["demo", "pricing", "pilot"]),
+    notes: z.string().max(1000).optional(),
+    newsletter: z.boolean().optional(),
+  }),
+  { name: "LeadCaptureModel" },
+);
+
+export const LeadCaptureForm = defineFormSpec({
+  meta: {
+    key: "marketing.lead.form",
+    version: "1.0.0",
+    title: "Lead capture form",
+    description: "Collect qualified OSS and Studio leads.",
+    domain: "marketing",
+    owners: ["@growth"],
+    tags: ["forms", "leads"],
+    stability: "experimental",
+  },
+  model: LeadCaptureModel,
+  layout: {
+    columns: responsiveFormColumns(2),
+    gap: "md",
+    flow: {
+      kind: "sections",
+      sections: [
+        { key: "identity", titleI18n: "Who you are", fieldNames: ["fullName", "email", "company"] },
+        { key: "request", titleI18n: "What you need", fieldNames: ["intent", "notes", "newsletter"] },
+      ],
+    },
+  },
+  fields: [
+    { kind: "text", name: "fullName", labelI18n: "Full name", required: true, autoComplete: "name" },
+    { kind: "email", name: "email", labelI18n: "Work email", required: true, autoComplete: "email" },
+    { kind: "text", name: "company", labelI18n: "Company", required: true, autoComplete: "organization" },
+    {
+      kind: "select",
+      name: "intent",
+      labelI18n: "Primary goal",
+      required: true,
+      options: [
+        { labelI18n: "Book a demo", value: "demo" },
+        { labelI18n: "Understand pricing", value: "pricing" },
+        { labelI18n: "Plan a pilot", value: "pilot" },
+      ],
+    },
+    { kind: "textarea", name: "notes", labelI18n: "Context", rows: 4, layout: { colSpan: "full" } },
+    { kind: "checkbox", name: "newsletter", labelI18n: "Send product updates" },
+  ],
+  actions: [{ key: "submit", labelI18n: "Send request", op: { name: "lead.create", version: "1.0.0" } }],
+  policy: { flags: ["lead-capture"], pii: ["fullName", "email", "company", "notes"] },
+  renderHints: { ui: "shadcn", form: "react-hook-form" },
+});
+
+export const formRegistry = new FormRegistry().register(LeadCaptureForm);`;
+
+export const leadCapturePanelCode = `"use client";
+
+import { formRenderer } from "@contractspec/lib.design-system/renderers/form-contract";
+import { LeadCaptureForm } from "../contracts/forms/lead-capture.form";
+
+export function LeadCapturePanel() {
+  return formRenderer.render(LeadCaptureForm, {
+    defaultValues: { newsletter: true },
+    overrides: {
+      onSubmitOverride: async (values, actionKey) => {
+        await fetch("/api/leads", {
+          method: "POST",
+          headers: { "content-type": "application/json" },
+          body: JSON.stringify({ actionKey, values }),
+        });
+      },
+    },
+  });
+}`;
+
+export const formShowcaseTemplateCode = `bun add @contractspec/example.form-showcase
+
+# Full form-only example docs
+open https://www.contractspec.io/docs/examples/form-showcase
+
+# Template catalog filtered to forms
+open https://www.contractspec.io/templates?tag=forms
+
+# Sandbox spec preview
+open https://www.contractspec.io/sandbox?template=form-showcase`;

package/src/components/docs/guides/GuideContractDrivenFormsPage.tsx

@@ -0,0 +1,143 @@
+import { CodeBlock } from '@contractspec/lib.design-system';
+import { HStack, VStack } from '@contractspec/lib.design-system/layout';
+import { List, ListItem } from '@contractspec/lib.design-system/list';
+import {
+	Code,
+	H1,
+	H2,
+	H3,
+	P,
+	Text,
+} from '@contractspec/lib.design-system/typography';
+import Link from '@contractspec/lib.ui-link';
+import { ChevronRight } from 'lucide-react';
+import { StudioPrompt } from '../shared/StudioPrompt';
+import {
+	formShowcaseTemplateCode,
+	leadCaptureFormCode,
+	leadCapturePanelCode,
+} from './GuideContractDrivenFormsPage.content';
+
+export function GuideContractDrivenFormsPage() {
+	return (
+		<VStack className="space-y-8">
+			<VStack className="space-y-3">
+				<H1 className="font-bold text-4xl">Build a contract-driven form</H1>
+				<P className="text-lg text-muted-foreground">
+					Define form data, fields, layout, policy, and submit behavior once,
+					then let your app render from the same ContractSpec surface.
+				</P>
+			</VStack>
+
+			<VStack className="card-subtle space-y-4 p-6">
+				<H2 className="font-bold text-2xl">What you'll build</H2>
+				<List className="space-y-2 text-muted-foreground text-sm">
+					<ListItem>
+						<Text>A schema-backed FormSpec for a lead capture form.</Text>
+					</ListItem>
+					<ListItem>
+						<Text>
+							A FormRegistry that exposes the latest version by stable key.
+						</Text>
+					</ListItem>
+					<ListItem>
+						<Text>
+							A React renderer that keeps UI, validation, and policy aligned.
+						</Text>
+					</ListItem>
+				</List>
+			</VStack>
+
+			<VStack className="space-y-6">
+				<VStack className="space-y-3">
+					<H2 className="font-bold text-2xl">1) Define the form spec</H2>
+					<P className="text-muted-foreground text-sm">
+						Create <Code>src/contracts/forms/lead-capture.form.ts</Code>:
+					</P>
+					<CodeBlock
+						language="typescript"
+						filename="src/contracts/forms/lead-capture.form.ts"
+						code={leadCaptureFormCode}
+					/>
+				</VStack>
+
+				<VStack className="card-subtle space-y-3 p-6">
+					<H3 className="font-semibold text-lg">Need every form field?</H3>
+					<P className="text-muted-foreground text-sm">
+						Start from the{' '}
+						<Link href="/docs/examples/form-showcase">
+							Form Showcase example
+						</Link>{' '}
+						or the{' '}
+						<Link href="/templates?tag=forms">form template catalog</Link>. It
+						is focused only on forms and covers field kinds, section layouts,
+						step layouts, arrays, groups, conditionals, and validation hints.
+					</P>
+					<CodeBlock
+						language="bash"
+						filename="form-showcase-template"
+						code={formShowcaseTemplateCode}
+					/>
+				</VStack>
+
+				<VStack className="space-y-3">
+					<H2 className="font-bold text-2xl">2) Render from the contract</H2>
+					<P className="text-muted-foreground text-sm">
+						Use the shared renderer, or provide your own driver if your app uses
+						a different component library.
+					</P>
+					<CodeBlock
+						language="tsx"
+						filename="src/components/LeadCapturePanel.tsx"
+						code={leadCapturePanelCode}
+					/>
+				</VStack>
+
+				<VStack className="space-y-3">
+					<H2 className="font-bold text-2xl">3) Validate and evolve</H2>
+					<CodeBlock
+						language="bash"
+						filename="validate-form"
+						code={`contractspec validate src/contracts/forms/lead-capture.form.ts`}
+					/>
+					<P className="text-muted-foreground text-sm">
+						Expected output: <Code>Validation passed</Code>. When the form
+						becomes public contract surface, version changes deliberately
+						instead of editing field meaning in place.
+					</P>
+				</VStack>
+
+				<VStack className="card-subtle space-y-3 p-6">
+					<H3 className="font-semibold text-lg">Repo tutorial</H3>
+					<P className="text-muted-foreground text-sm">
+						The repository guide adds the longer implementation checklist,
+						custom renderer notes, and rollout rules.
+					</P>
+					<CodeBlock
+						language="bash"
+						filename="repo-guide"
+						code={`open docs/tutorials/contract-driven-forms.md`}
+					/>
+				</VStack>
+
+				<StudioPrompt
+					title="Need governed form changes?"
+					body="Studio can connect form edits to customer evidence, approval packets, and rollout checks before teams regenerate public surfaces."
+				/>
+			</VStack>
+
+			<HStack className="flex items-center gap-4 pt-4">
+				<Link
+					href="/docs/guides/generate-docs-clients-schemas"
+					className="btn-primary"
+				>
+					<Text>Next: Generate docs + clients</Text>
+					<ChevronRight size={16} />
+				</Link>
+				<Link href="/docs/guides" className="btn-ghost">
+					<Text>Back to guides</Text>
+				</Link>
+			</HStack>
+		</VStack>
+	);
+}

package/src/components/docs/guides/GuideSpecValidationTypingPage.tsx

@@ -144,10 +144,10 @@ bun run validate`}
 
 			<div className="flex items-center gap-4 pt-4">
 				<Link
-					href="/docs/guides/generate-docs-clients-schemas"
+					href="/docs/guides/contract-driven-forms"
 					className="btn-primary"
 				>
-					Next: Generate docs + clients <ChevronRight size={16} />
+					Next: Contract-driven forms <ChevronRight size={16} />
 				</Link>
 				<Link href="/docs/guides" className="btn-ghost">
 					Back to guides

package/src/components/docs/guides/GuidesIndexPage.tsx

@@ -24,6 +24,13 @@ const guides = [
 		href: '/docs/guides/spec-validation-and-typing',
 		time: '20 min',
 	},
+	{
+		title: 'Build a contract-driven form',
+		description:
+			'Use FormSpec to keep data shape, fields, layout, policy, and submit behavior aligned.',
+		href: '/docs/guides/contract-driven-forms',
+		time: '25 min',
+	},
 	{
 		title: 'Generate docs and clients',
 		description:

package/src/components/docs/guides/guides.docblocks.ts

@@ -37,6 +37,18 @@ Create a single OperationSpec, register it, and expose it through a Next.js App
 		body: `# Spec-driven validation and typing
 
 Define command/query specs that enforce validation and generate types without rewriting your app.`,
+	},
+	{
+		id: 'docs.guides.contract-driven-forms',
+		title: 'Contract-driven forms',
+		summary: 'Define schema-backed FormSpec surfaces and render them safely.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/guides/contract-driven-forms',
+		tags: ['guides', 'forms', 'ui'],
+		body: `# Build a contract-driven form
+
+Define a FormSpec with model, fields, layout, policy, and actions, then render it through a shared or app-specific renderer.`,
 	},
 	{
 		id: 'docs.guides.docs-clients-schemas',

package/src/components/docs/guides/index.ts

@@ -2,6 +2,7 @@ import './guides.docblocks';
 
 export { GuideCIDiffGatingPage } from './GuideCIDiffGatingPage';
 export { GuideConnectInRepoPage } from './GuideConnectInRepoPage';
+export { GuideContractDrivenFormsPage } from './GuideContractDrivenFormsPage';
 export { GuideContractTypesPage } from './GuideContractTypesPage';
 export { GuideDocsPipelinePage } from './GuideDocsPipelinePage';
 export { GuideFirstModuleBundlePage } from './GuideFirstModuleBundlePage';

package/src/components/docs/libraries/LibrariesApplicationShellPage.content.ts

@@ -0,0 +1,170 @@
+export const shellUsageExample = `import {
+  AppShell,
+  PageOutline,
+  type AppShellNavigationSection,
+  type PageOutlineItem,
+} from "@contractspec/lib.design-system/shell";
+
+const navigation: AppShellNavigationSection[] = [
+  {
+    title: "Workspace",
+    items: [
+      { label: "Dashboard", href: "/dashboard" },
+      {
+        label: "Contracts",
+        href: "/contracts",
+        children: [
+          { label: "Operations", href: "/contracts/operations" },
+          { label: "Events", href: "/contracts/events" },
+        ],
+      },
+    ],
+  },
+];
+
+const outline: PageOutlineItem[] = [
+  {
+    id: "architecture",
+    label: "Architecture",
+    level: 1,
+    children: [
+      { id: "desktop", label: "Desktop shell", level: 2 },
+      { id: "mobile", label: "Mobile adaptation", level: 2 },
+    ],
+  },
+];
+
+export function WorkspacePage() {
+  return (
+    <AppShell
+      brand={{ label: "ContractSpec", href: "/dashboard" }}
+      navigation={navigation}
+      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" />}
+    >
+      <main>{/* route content */}</main>
+    </AppShell>
+  );
+}`;
+
+export const scratchPrompt = `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.
+
+Use this architecture:
+- Keep route content independent from navigation chrome.
+- Create a typed navigation model with sections, items, active state, optional children, badges, icons, disabled items, and href/onSelect support.
+- 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.
+- Expose the system from the design system or a dedicated shell module, not from a single app route.
+
+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.
+- 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.
+- 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.
+
+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.
+- Update docs and exports so developers can import the shell from a stable public API.
+
+Deliverables:
+- Typed shell models.
+- Web shell components.
+- Native shell components or adapters.
+- PageOutline component with three-level support.
+- Usage example.
+- Focused tests and typecheck/build evidence.`;
+
+export const refactorPrompt = `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.
+
+Start by auditing:
+- Current layout wrappers and route groups.
+- Sidebar, topbar, breadcrumb, command/search, auth menu, and mobile navigation implementations.
+- 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.
+
+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.
+
+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 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.
+- 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.`;
+
+export const shellParts = [
+	{
+		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.',
+	},
+] as const;

package/src/components/docs/libraries/LibrariesApplicationShellPage.tsx

@@ -0,0 +1,112 @@
+import { CodeBlock, InstallCommand } from '@contractspec/lib.design-system';
+import { Box, HStack, VStack } from '@contractspec/lib.design-system/layout';
+import {
+	Code,
+	H1,
+	H2,
+	H3,
+	P,
+	Text,
+} from '@contractspec/lib.design-system/typography';
+import Link from '@contractspec/lib.ui-link';
+import { ChevronRight } from 'lucide-react';
+import {
+	refactorPrompt,
+	scratchPrompt,
+	shellParts,
+	shellUsageExample,
+} from './LibrariesApplicationShellPage.content';
+
+export function LibrariesApplicationShellPage() {
+	return (
+		<VStack className="space-y-8">
+			<VStack className="space-y-4">
+				<H1 className="font-bold text-4xl">Application shell</H1>
+				<P className="text-lg text-muted-foreground">
+					A reusable navigation system for product apps: desktop sidebar, topbar
+					breadcrumbs, command search, account actions, mobile adapters, and a
+					Notion-style <Code>PageOutline</Code> for page sections.
+				</P>
+			</VStack>
+
+			<VStack className="space-y-4">
+				<H2 className="font-bold text-2xl">Installation</H2>
+				<InstallCommand package="@contractspec/lib.design-system" />
+			</VStack>
+
+			<VStack className="space-y-4">
+				<H2 className="font-bold text-2xl">What It Standardizes</H2>
+				<Box className="grid gap-4 md:grid-cols-2">
+					{shellParts.map((part) => (
+						<Box key={part.title} className="card-subtle p-4">
+							<H3 className="font-semibold">{part.title}</H3>
+							<P className="mt-2 text-muted-foreground text-sm leading-7">
+								{part.body}
+							</P>
+						</Box>
+					))}
+				</Box>
+			</VStack>
+
+			<VStack className="space-y-4">
+				<H2 className="font-bold text-2xl">Import Surface</H2>
+				<P className="text-muted-foreground">
+					The shell is exposed as a focused design-system subpath so apps can
+					adopt navigation chrome without pulling unrelated documentation or
+					marketing helpers.
+				</P>
+				<CodeBlock
+					language="tsx"
+					filename="app-shell-example.tsx"
+					code={shellUsageExample}
+				/>
+			</VStack>
+
+			<VStack className="space-y-4">
+				<H2 className="font-bold text-2xl">AI Prompt: Build From Scratch</H2>
+				<P className="text-muted-foreground">
+					Use this prompt when the app does not already have a shell or when the
+					design-system package needs the reusable primitive first.
+				</P>
+				<CodeBlock
+					language="markdown"
+					filename="implement-application-shell.md"
+					code={scratchPrompt}
+				/>
+			</VStack>
+
+			<VStack className="space-y-4">
+				<H2 className="font-bold text-2xl">AI Prompt: Refactor An App</H2>
+				<P className="text-muted-foreground">
+					Use this prompt when an app already has custom navigation chrome and
+					needs to migrate without breaking route behavior.
+				</P>
+				<CodeBlock
+					language="markdown"
+					filename="refactor-to-application-shell.md"
+					code={refactorPrompt}
+				/>
+			</VStack>
+
+			<VStack className="card-subtle space-y-3 p-6">
+				<H2 className="font-bold text-2xl">Naming</H2>
+				<P className="text-muted-foreground">
+					Use <Code>AppShell</Code> for the whole navigation frame and{' '}
+					<Code>PageOutline</Code> 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.
+				</P>
+			</VStack>
+
+			<HStack className="flex flex-wrap items-center gap-3 pt-2">
+				<Link href="/docs/libraries/cross-platform-ui" className="btn-ghost">
+					<Text>Cross-platform UI</Text>
+				</Link>
+				<Link href="/docs/libraries/design-system" className="btn-primary">
+					<Text>Design System</Text> <ChevronRight size={16} />
+				</Link>
+			</HStack>
+		</VStack>
+	);
+}