export declare const layerCards: readonly [{
    readonly title: "@contractspec/lib.presentation-runtime-core";
    readonly body: "Shared state, table models, workflow logic, visualization helpers, and the alias helpers consumed by web and native builds.";
}, {
    readonly title: "@contractspec/lib.presentation-runtime-react";
    readonly body: "React-facing hooks such as useContractTable, useDataViewTable, and useWorkflow. This is the shared hook surface most product code starts from.";
}, {
    readonly title: "@contractspec/lib.presentation-runtime-react-native";
    readonly body: "Native entrypoint for mobile apps. It re-exports the shared table and data-view hooks so the controller API stays aligned with the React package.";
}, {
    readonly title: "@contractspec/lib.ui-kit-web";
    readonly body: "Browser-first primitives and accessibility helpers. Reach for this layer when you want direct control over the web renderer.";
}, {
    readonly title: "@contractspec/lib.ui-kit";
    readonly body: "Native-first primitives for Expo and React Native. Reach for this layer when the render surface should stay mobile-native.";
}, {
    readonly title: "@contractspec/lib.design-system";
    readonly body: "Composed components, ThemeSpec/TranslationSpec-aware controls, token helpers, and paired web/mobile implementations that sit on top of both UI kits.";
}];
export declare const hookCards: readonly [{
    readonly title: "useContractTable";
    readonly body: "Use this when your rows and column definitions already live in product code and you want one headless controller for sorting, pagination, selection, visibility, pinning, sizing, and expansion.";
}, {
    readonly title: "useDataViewTable";
    readonly body: "Use this when the table should stay driven by a DataViewSpec instead of hand-authored columns. It adapts the spec to the same generic controller model.";
}, {
    readonly title: "Native re-export boundary";
    readonly body: "On native apps, import the same hook names from @contractspec/lib.presentation-runtime-react-native when you want the import path itself to signal a mobile boundary.";
}];
export declare const aliasSetupCards: readonly [{
    readonly title: "Next.js / Turbopack";
    readonly body: "Use withPresentationTurbopackAliases as the default path in current Next.js apps. It patches nextConfig.turbopack instead of mutating a webpack config object.";
}, {
    readonly title: "Next.js / Webpack fallback";
    readonly body: "Use withPresentationWebpackAliases only when a Next.js app explicitly opts back into webpack via the CLI flags.";
}, {
    readonly title: "Expo / Metro";
    readonly body: "Use withPresentationMetroAliases on Metro when native platforms should resolve web ui-kit /ui imports and the shared React runtime root to native implementations.";
}];
export declare const designSystemHelperCards: readonly [{
    readonly title: "withPlatformUI";
    readonly body: "Use this lightweight adapter when a design-system surface needs one object that carries the current platform, tokens, and breakpoints.";
}, {
    readonly title: "mapTokensForPlatform";
    readonly body: "Use this when resolved tokens need to be mapped into platform-specific token shapes before the final renderer consumes them.";
}];
export declare const remapCards: readonly [{
    readonly title: "What Webpack remaps";
    readonly items: readonly ["@contractspec/lib.ui-kit -> @contractspec/lib.ui-kit-web", "@contractspec/lib.presentation-runtime-react-native -> @contractspec/lib.presentation-runtime-react", "Prepends .web.js, .web.jsx, .web.ts, and .web.tsx to webpack resolve.extensions"];
}, {
    readonly title: "What Turbopack remaps";
    readonly items: readonly ["@contractspec/lib.ui-kit -> @contractspec/lib.ui-kit-web", "@contractspec/lib.presentation-runtime-react-native -> @contractspec/lib.presentation-runtime-react", "Initializes or merges turbopack.resolveExtensions with a web-first extension list"];
}, {
    readonly title: "What Metro remaps";
    readonly items: readonly ["@contractspec/lib.ui-kit-web/ui/* -> @contractspec/lib.ui-kit/ui/* on ios/android/native/mobile", "Root @contractspec/lib.presentation-runtime-react -> @contractspec/lib.presentation-runtime-react-native", "Enables package exports and expands platform resolution ordering"];
}];
export declare const layoutRules: readonly ["Set gap, align, justify, and wrap explicitly in shared code because defaults are not identical between web and native.", "Shared-safe subset: VStack, HStack, and Box with className, gap, align, justify, and wrap.", "Web-only feature: as lets stack primitives emit semantic elements such as section, header, main, or article.", "Native-only extras: spacing, width, and padding exist on the native stack primitives and should stay out of shared renderer code.", "HStack and Box reverse-wrap tokens differ: wrapReverse on web, reverse on native. Prefer nowrap or wrap in shared code.", "Box defaults to nowrap on web and wrap on native, so shared code should set wrap intentionally."];
export declare const gotchas: readonly ["withPresentationNextAliases no longer exists. Use withPresentationTurbopackAliases for the default Next.js path or withPresentationWebpackAliases for explicit webpack fallback.", "Prefer root runtime imports when alias helpers matter. Metro remaps the root @contractspec/lib.presentation-runtime-react package, not arbitrary deep hook subpaths.", "Metro only rewrites @contractspec/lib.ui-kit-web/ui/* imports. Router-specific web packages and other web-only helpers still need platform-aware imports.", "presentation-runtime-core is headless. It owns models and config helpers, not rendered React components.", "design-system compatibility comes from paired .tsx / .native.tsx implementations and token helpers such as withPlatformUI and mapTokensForPlatform.", "Form controls should come from @contractspec/lib.design-system when product code needs ThemeSpec or TranslationSpec support.", "Stack primitives are similar across platforms, but the prop surface is not identical. Stay inside the common subset for shared renderers.", "Alias helpers solve module resolution only. They do not replace app-level monorepo watchFolders, Expo Router setup, or other Next configuration."];
export declare const markdownKitIntro = "Copy these markdown snippets into your own AGENTS.md, LLM guide, README, or engineering playbook when you want to enforce the same cross-surface rules across customer projects.";
export declare const turbopackAliasExample = "import { withPresentationTurbopackAliases } from '@contractspec/lib.presentation-runtime-core';\n\n/** @type {import('next').NextConfig} */\nconst nextConfig = withPresentationTurbopackAliases({\n  turbopack: {\n    resolveAlias: {\n      fs: { browser: 'browserify-fs' },\n    },\n  },\n});\n\nexport default nextConfig;";
export declare const webpackAliasExample = "import { withPresentationWebpackAliases } from '@contractspec/lib.presentation-runtime-core';\n\n/** @type {import('next').NextConfig} */\nconst nextConfig = {\n  webpack: (config) => withPresentationWebpackAliases(config),\n};\n\nexport default nextConfig;";
export declare const metroAliasExample = "const { getDefaultConfig } = require('expo/metro-config');\nconst {\n  withPresentationMetroAliases,\n} = require('@contractspec/lib.presentation-runtime-core');\n\nconst projectRoot = __dirname;\nconst config = getDefaultConfig(projectRoot);\n\nmodule.exports = withPresentationMetroAliases(config);";
export declare const designSystemHelperExample: string;
export declare const stackExample = "import { Box, HStack, VStack } from '@contractspec/lib.ui-kit-web/ui/stack';\n\nexport function AccountSummaryHeader() {\n  return (\n    <VStack gap=\"lg\" align=\"stretch\" className=\"w-full\">\n      <HStack gap=\"sm\" align=\"center\" justify=\"between\" wrap=\"wrap\">\n        <Box gap=\"xs\" align=\"center\" justify=\"start\" wrap=\"nowrap\">\n          <StatusDot />\n          <Title />\n        </Box>\n        <Actions />\n      </HStack>\n      <Filters />\n    </VStack>\n  );\n}\n\n// In native-only files, swap the import to:\n// @contractspec/lib.ui-kit/ui/stack\n//\n// On web-only pages, VStack / HStack / Box also support:\n// <VStack as=\"section\">...</VStack>";
export declare const renderingExample = "import { DataTable as DesignSystemTable } from '@contractspec/lib.design-system';\nimport { DataTable as NativeTable } from '@contractspec/lib.ui-kit/ui/data-table';\nimport { DataTable as WebTable } from '@contractspec/lib.ui-kit-web/ui/data-table';\nimport { useContractTable } from '@contractspec/lib.presentation-runtime-react';\n\nexport function useAccountsController(data, columns) {\n  return useContractTable({\n    data,\n    columns,\n    selectionMode: 'single',\n    initialState: {\n      sorting: [{ id: 'arr', desc: true }],\n      pagination: { pageIndex: 0, pageSize: 5 },\n    },\n  });\n}\n\nexport function WebAccounts({ controller }) {\n  return <WebTable controller={controller} />;\n}\n\nexport function NativeAccounts({ controller }) {\n  return <NativeTable controller={controller} />;\n}\n\nexport function ProductAccounts({ controller }) {\n  return (\n    <DesignSystemTable\n      controller={controller}\n      title=\"Accounts\"\n      description=\"Same controller, composed ContractSpec shell.\"\n    />\n  );\n}\n\n// If the table is spec-driven instead of hand-authored,\n// swap useContractTable for useDataViewTable.";
export declare const customerPolicyMarkdown = "# Cross-Surface Rendering Policy\n\n- Import runtime bundler helpers from `@contractspec/lib.presentation-runtime-core` root only.\n- Use `withPresentationTurbopackAliases` for default Next.js projects.\n- Use `withPresentationWebpackAliases` only when the app explicitly opts into webpack.\n- Use `withPresentationMetroAliases` for Expo and Metro builds.\n- Prefer `@contractspec/lib.design-system` for shared product-facing surfaces.\n- Use design-system controls when a field must respect ThemeSpec component variants or TranslationSpec messages.\n- Use `@contractspec/lib.ui-kit-web` only for web-specific primitive lanes.\n- Use `@contractspec/lib.ui-kit` only for native-specific primitive lanes.\n- Keep shared layout code inside the common `VStack` / `HStack` / `Box` subset.\n- Do not use removed `withPresentationNextAliases`.\n- Treat `.tsx` / `.native.tsx` pairs as the standard design-system compatibility boundary.";
export declare const customerChecklistMarkdown = "# Cross-Surface Rendering Checklist\n\n1. Configure the bundler aliases before sharing any UI code.\n2. Choose the controller layer:\n   - use `useContractTable` for app-owned rows and columns\n   - use `useDataViewTable` for DataViewSpec-driven tables\n3. Choose the renderer lane:\n   - web primitive: `@contractspec/lib.ui-kit-web`\n   - native primitive: `@contractspec/lib.ui-kit`\n   - shared product surface: `@contractspec/lib.design-system`\n4. Verify mirrored `.tsx` / `.native.tsx` implementations where the design-system owns the surface.\n5. Wrap product surfaces in `DesignSystemThemeProvider` and `DesignSystemTranslationProvider` when ThemeSpec or TranslationSpec data is available.\n6. In shared layout code, set `gap`, `align`, `justify`, and `wrap` explicitly.\n7. Check docs and examples for root imports and current helper names before copying them into product code.";
