{"_id":"@18studio/aicloud-uikit-react","name":"@18studio/aicloud-uikit-react","dist-tags":{"latest":"0.1.0"},"versions":{"0.1.0":{"name":"@18studio/aicloud-uikit-react","version":"0.1.0","description":"Web React AI Cloud UIKIT components, composition contracts, adapters, examples, tests, and documentation.","type":"module","exports":{".":{"types":"./dist/index.d.ts","import":"./dist/index.js"}},"types":"./dist/index.d.ts","dependencies":{"@18studio/aicloud-uikit-core":"0.1.0","@18studio/aicloud-uikit-tokens":"0.1.0","@radix-ui/react-checkbox":"^1.1.3","@radix-ui/react-popover":"^1.1.6","@radix-ui/react-select":"^2.1.6","@radix-ui/react-switch":"^1.1.3","@tanstack/react-table":"^8.20.5","@tanstack/react-virtual":"^3.11.2","@xyflow/react":"^12.3.5","@hookform/resolvers":"^3.9.1","class-variance-authority":"^0.7.1","clsx":"^2.1.1","echarts":"^5.5.1","lucide-react":"^0.468.0","monaco-editor":"^0.52.2","react-hook-form":"^7.53.2","tailwind-merge":"^2.6.0","zod":"^3.23.8"},"peerDependencies":{"react":">=18","react-dom":">=18"},"scripts":{"build":"node ../../scripts/build-package.mjs","check":"node ../../scripts/check-boundaries.mjs && node ../../scripts/check-react-primitives.mjs && node ../../scripts/check-react-shell.mjs && node ../../scripts/check-react-tables.mjs && node ../../scripts/check-react-forms.mjs && node ../../scripts/check-react-governance.mjs && node ../../scripts/check-react-operations.mjs && node ../../scripts/check-react-runtime.mjs && node ../../scripts/check-react-application-runtime.mjs && node ../../scripts/check-react-compositions.mjs","prepack":"npm run build"},"publishConfig":{"access":"public"},"gitHead":"393fb6ab194cd4236476bd5a92610fd9a2a43923","_id":"@18studio/aicloud-uikit-react@0.1.0","_nodeVersion":"24.14.1","_npmVersion":"11.11.0","dist":{"integrity":"sha512-d3lQHOy3IHE9ak2C1OxXYFKP/58XsqiOPifVfI/bMUdarv6A3F5Dr05rj6rQWIogUkP2xtR6jM7W2kmDDItgnA==","shasum":"271ef72103a9e7f4390915baf8e6003e7b16747f","tarball":"https://registry.npmjs.org/@18studio/aicloud-uikit-react/-/aicloud-uikit-react-0.1.0.tgz","fileCount":6,"unpackedSize":608352,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIG9YURXkug+cwBBTYlebpBUXyKFmQ2ybdus6w6xdJnrtAiEA52YuC60oMdceCzfg1AW2aAZ9MbHRJxVsUU+aF0uJD5o="}]},"_npmUser":{"name":"p141592","email":"root@k0d.ru"},"directories":{},"maintainers":[{"name":"p141592","email":"root@k0d.ru"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/aicloud-uikit-react_0.1.0_1782015094496_0.1919966273445175"},"_hasShrinkwrap":false}},"time":{"created":"2026-06-21T04:11:34.301Z","0.1.0":"2026-06-21T04:11:34.643Z","modified":"2026-06-21T04:11:34.884Z"},"maintainers":[{"name":"p141592","email":"root@k0d.ru"}],"description":"Web React AI Cloud UIKIT components, composition contracts, adapters, examples, tests, and documentation.","readme":"# @18studio/aicloud-uikit-react\n\nWeb React component package for UIKIT v1.\n\n## Scope\n\n- React components, providers, hooks, adapters, examples, tests, and documentation.\n- May use Web-only libraries such as React DOM, Radix UI, Tailwind CSS 4, TanStack, ECharts, React Flow, Monaco, and browser focus APIs.\n- Public component contracts remain AI Cloud UIKIT contracts, not raw engine APIs.\n- Components must not fetch product APIs or own canonical data lifecycle.\n\n## Phase 3 status\n\nPhase 3 implements the React foundation and primitive/shared components:\n\n- `UikitProvider`, `useUikit`, `cn()`, `createVariants()`, icon slots, provider metadata, Tailwind token-class integration, and permission/state adapters.\n- Action components: `Button`, `IconButton`, `SplitButton`, `ActionMenu`, `CopyButton`, and `LinkAction`.\n- Field components: `Field`, `TextInput`, `TextArea`, `NumericInput`, `SearchInput`, `PasswordInput`, `OneTimeSecret`, `MarkdownEditor`, and `JsonEditor`.\n- Selection components: `Checkbox`, `RadioGroup`, `Switch`, `Select`, `EntitySelect`, `MultiSelect`, `EntityMultiSelect`, `Combobox`, and `SegmentedControl`.\n- Structured inputs: `DateTimeInput`, `DurationInput`, `MoneyInput`, `QuantityInput`, `KeyValueEditor`, `SchemaFieldRenderer`, `ExpressionEditor`, `CronScheduleEditor`, and `FileDropzone`.\n- Status and metadata: `StatusPill`, `RiskBadge`, `ClassificationBadge`, `EnvironmentBadge`, `PrincipalBadge`, `ReferenceLabel`, `Timestamp`, and `MetricValue`.\n- Feedback and state surfaces: `InlineNotice`, `ErrorBanner`, `ValidationSummary`, `EmptyState`, `Skeleton`, `Progress`, `ToastCenter`, `ConnectionState`, `PartialDataNotice`, `StaleDataNotice`, `MutationStatus`, `BatchResultSummary`, and `StateSurface`.\n\n## Phase 4 status\n\nPhase 4 implements shell, navigation, layout, and overlay components:\n\n- Shell/navigation: `AppShell`, `GlobalNav`, `ScopeSelector`, `RoleSwitcher`, `UniversalSearch`, `CommandPalette`, `NotificationCenter`, `ActivityCenter`, and `ContextHelpPanel`.\n- Structure: `PageHeader`, `Breadcrumbs`, `Tabs`, `Toolbar`, `Section`, `Panel`, `KeyValueList`, `ResourceSummary`, and `ResourceOverview`.\n- Overlays: `Modal`, `ConfirmationDialog`, `Drawer`, `DetailsEditDrawer`, `Popover`, and `Tooltip`.\n\nThe components provide responsive mobile/tablet/desktop layout semantics, permission-aware navigation and action affordances, focus and restore handling for dialogs/drawers, escape-key behavior, and dirty/pending guards for unsafe drawer close paths. They remain host-router agnostic: navigation props expose intent and hrefs, but the consuming application owns routing, persistence, API transport, and audit.\n\n## Phase 5 status\n\nPhase 5 implements tables and collections for enterprise resource lists:\n\n- `DataTable` with server-side search, filters, sorting, cursor pagination, column preferences, saved views, row selection, row actions, bulk actions, refresh, export, URL-compatible controlled state, contained horizontal scroll, keyboard row opening with Enter/Space, unknown-value rendering, and required-column protection.\n- Table states for loading, empty, no-result, partial, stale, error, unavailable, permission, and unknown values. Loading preserves geometry with skeleton rows; partial and stale states keep valid rows visible; permission and unavailable states use safe explanations supplied by the application.\n- Support components: `FilterBuilder`, `ActiveFilterBar`, `ColumnPicker`, `SavedViewPicker`, `BulkActionBar`, `CursorPagination`, `InlineEditRow`, `CollectionCard`, and `QueueList`.\n- TanStack Table and TanStack Virtual are declared as internal table-engine dependencies; the public contract remains `DataTable`, normalized `TableQuery`, core `ColumnDef`, and UIKIT intent callbacks.\n- TanStack Query integration examples live in `examples/preview/src/tables-query-example.ts` and `tanStackQueryIntegrationExamples`. They demonstrate loading, stale refresh, polling, and mutation adapter boundaries without direct product API calls in components.\n\nPhase 5 table events are server-side intent callbacks: search, filter, sort, paginate, select, column preference, saved view, refresh, export, row open, row action, and bulk action events report intent only. Consuming applications own URL serialization, persistence, server cache, query functions, mutation functions, audit, and export transport.\n\n## Phase 6 status\n\nPhase 6 complete for forms, editing, and creation:\n\n- `FormLayout` and `FormSection` compose accessible form structure, validation summaries, permission states, one/two-column responsive layouts, and application-owned submit intent callbacks.\n- `DirtyStateGuard` preserves entered values and blocks unsafe close, navigation, scope change, entity switch, or tab change when form or wizard state is dirty or pending.\n- `ConflictResolver`, `SemanticDiff`, and `RevisionPicker` preserve local input, show semantic differences, and expose reload, merge, or fork recovery intents without owning persistence or product API transport.\n- `Wizard` and `WizardStepNav` support complex creation with controlled step state, keyboard-operable step buttons, `aria-current=\"step\"`, disabled blocked steps, non-color status symbols, review sidebars, save-draft intent, and submit intent callbacks.\n- `ReviewStep` renders normalized `ReviewValue` summaries, redaction-aware values, validation issues, and semantic diffs before submission.\n- React Hook Form, Zod, and resolver adapters are available through `createReactHookFormAdapter()`, `createZodValidationAdapter()`, and `createHookFormResolverAdapter()`. These adapters are optional: schemas are not UIKIT-only requirement and components do not require schema props.\n- Editing rules are enforced and documented through `editingSurfaceRules`, `validateEditingSurfaceUsage()`, and `data-editing-surface` markers: use `DetailsEditDrawer` for non-trivial existing entities, `InlineEditRow` for simple row-complete entities, and `Wizard` for complex creation; no separate details/edit overlays may be created for the same entity.\n\nForm values, wizard drafts, canonical saves, conflict reload/merge/fork, audit, and product API transport remain application-owned persistence. UIKIT components expose normalized models, supplied permissions, validation issues, dirty decisions, and intent callbacks only.\n\n## Phase 7 status\n\nPhase 7 complete for governance, approvals, policy review, and release safety surfaces:\n\n- Policy and permission surfaces: `PermissionExplanation`, `EffectivePolicyViewer`, `PolicyRuleEditor`, and `PolicyInheritanceDiagram` render only application-supplied policy semantics, omit denied rules, and show redacted placeholders instead of restricted content.\n- Review and approval surfaces: `ImpactPreview`, `RiskSummary`, `ApprovalPackageView`, `ApprovalDecisionPanel`, and `ReviewQueueTable` expose approval and review intent callbacks only; approval decisions require supplied permission and auditable context before submit; audit reason required states keep unsafe actions disabled until applications provide context.\n- Validation and evaluation surfaces: `ValidationResults` and `EvaluationScorecard` display normalized validation and score evidence with visual state markers, non-color text/status labels, and redaction-aware values.\n- Release safety surfaces: `ReleaseGateSummary`, `DependencyDiff`, `ReleaseBundleView`, `ReleaseTimeline`, and `RollbackSelector` cover gates, dependency changes, bundles, timelines, and rollback/restore selection without owning product release policy or transport.\n- Dangerous or destructive actions such as policy deletion, approval rejection, destructive impact review, and rollback are permission-safe, disabled when audit context is missing, and marked with `data-audit-required` for application audit pipelines.\n\nRestricted governance, approval, validation, dependency, evidence, and release content is omitted or redacted before render. Business policy semantics, risk scoring, gate evaluation, approval persistence, audit record creation, rollback execution, and product API transport remain application-owned.\n\n## Phase 8 status\n\nPhase 8 complete for operations, evidence, timelines, traces, charts, and graphs:\n\n- Operations components: `RunStatusPanel`, `RecoveryPanel`, `OperationsStatusBoard`, and `EvidenceList` consume normalized run controls, recovery options, trace summaries, audit records, evidence refs, citations, supplied permissions, and intent callbacks only.\n- Timeline/trace components: `UnifiedTimeline` merges timeline events, annotations, audits, and trace summaries; `TraceWaterfall` renders trace spans with duration text and table/list-readable information.\n- Graph components: `DependencyGraph`, `LineageGraph`, `WorkflowGraph`, `TopologyExplorer`, `GraphLegendView`, and `RelationshipTable` consume normalized `GraphNode`, `GraphEdge`, `GraphLegend`, and `RelationshipTableRow` contracts.\n- Chart components: `MetricChart`, `TimeSeriesChart`, `DistributionChart`, `ComparisonChart`, `CapacityBar`, `RankedBarChart`, `CompositionChart`, `TimeCellMatrix`, `MetricTable`, and `TimeRangePicker` consume `NormalizedMetricSeries`, `TimeRange`, `Threshold`, and `TimelineAnnotation` without exposing engine option objects.\n- ECharts and @xyflow/react are dynamically loaded internal defaults when available; SVG/CSS/list/table fallbacks and table fallbacks are always available, including `MetricTable` and `RelationshipTable` textual alternatives.\n- Data-quality states are visible through text labels and `data-quality`; reduced motion is accepted through props or `UikitProvider`.\n\nOperations policy, run execution, recovery execution, evidence retrieval, graph discovery, metric queries, audit persistence, and product API transport remain application-owned.\n\n## Phase 9 status\n\nPhase 9 complete for technical and runtime surfaces:\n\n- Code and editing surfaces: `CodeBlock` and `YAMLEditor` expose copy/export/validate intents, redaction placeholders, and lazy Monaco loading as an internal default with a textarea fallback rather than public Monaco APIs.\n- Output surfaces: `LogViewer` and `Terminal` preserve buffered output during disconnected/reconnecting states, expose copy/export/download/terminal-signal intents only, and avoid permanent keyboard traps by releasing terminal focus on Escape.\n- Inspection surfaces: `PayloadInspector`, `SchemaViewer`, and `DiffViewer` render normalized payload, schema, and diff models with permission and redaction states before visible content.\n- Runtime resource surfaces: `FileTree`, `ArtifactList`, `WorkspacePanel`, `SnapshotList`, `DiffSummary`, `WorktreeStatus`, `MountList`, and `ScanResultList` cover file, artifact, workspace, snapshot, diff, worktree, mount, and scan result workflows with state/intent callbacks only.\n- Copy, export, download, permission, and redaction examples live in `examples/preview/src/technical-runtime-example.ts`.\n\nWorkspace file retrieval, artifact download transport, terminal process execution, log streaming, schema validation semantics, scan execution, mount execution, snapshot restore execution, audit persistence, and product API transport remain application-owned.\n\n## Phase 10 status\n\nPhase 10 complete for application runtime surfaces:\n\n- Business-language-first runtime entry: `DomainActionLauncher` and `DynamicForm` model domain outcomes, required business inputs, permissions, and state/intent callbacks without making prompt entry the primary contract.\n- Results and artifacts: `ResultCard`, `ResultTable`, and `EditableArtifact` render normalized result summaries, citation evidence, artifact references, dirty-state editing, and feedback intents.\n- Conversation and streaming: `ConversationThread` and `StreamingResponse` render accessible streaming with `aria-live`, `aria-busy`, retention-boundary metadata, and forbidden-history tests that omit excluded or forbidden retained messages before render.\n- Required input, approvals, and runs: `RequiredInputPrompt`, `RuntimeApprovalCard`, and `ApplicationRunStatus` expose required input, runtime approval, audit reason, run step, and run control intents only.\n- Feedback and channels: `FeedbackControl` and `ChannelPreview` support permission-aware feedback and channel previews with citation, artifact, retention-boundary, and application-owned send intents.\n\nRuntime transport, product API transport remain application-owned, as do model execution, channel delivery, approval persistence, feedback persistence, conversation retention selection, audit storage, and server state. Components consume normalized models, supplied permission decisions, and state/intent callbacks only.\n\n## Phase 11 status\n\nPhase 11 complete for reusable domain composition contracts and examples:\n\n- `DomainCompositionWorkbench`, `CompositionSlotList`, and `CompositionTraceabilityTable` render normalized `DomainCompositionContract`, `CompositionSlotContract`, and `CompositionTraceabilityEntry` models.\n- Composition domains cover Managed Models, Knowledge & Retrieval, MCP, Agent, Workflow, AI Application, Context, Workspace, Organization, IAM/Security, Policy, Capacity, Registry, Connectors, Assurance, Observability & Audit, GPU Telemetry & Profiling, and SaaS Operations.\n- UF-001 through UF-100 support is verified through composition traceability, not business-flow implementation; each UF row maps to existing reusable UIKIT slots such as shell, tables, forms, governance, operations, technical runtime, and application runtime components.\n- The no-local-fork policy is explicit: reject local forks in favor of variants/slots/documented composition, and keep domain-specific orchestration, runtime transport, telemetry collection, profiling capture, audit persistence, SaaS operations execution, and product API transport remain application-owned.\n- Responsive and permission behavior is inherited from reusable slots and reinforced by `md`/`xl` layout markers, `PermissionDecision` filtering, and `data-no-local-fork` evidence markers.\n\n## Phase 12 status\n\nPhase 12 complete for cross-catalog quality gates:\n\n- Cross-catalog accessibility and responsive evidence verifies tables, forms, governance, operations, technical runtime, application runtime, and domain compositions retain semantic labels, `aria-live`/`aria-busy`, keyboard escape/release paths, table alternatives, and `md`/`xl` responsive behavior instead of removing accessibility alternatives to pass performance.\n- Security/permission/redaction checks cover dangerous action gates, `data-audit-required` audit-context requirements, omitted denied rows, redaction placeholders, and guarded copy/export/download/terminal/code/payload/artifact/secret-adjacent transport paths with `data-redaction-transport-guard` markers.\n- Error, trace, citation, and audit leakage checks preserve safe `StateSurface` errors, trace/citation redaction, audit reason requirements, and application-owned product API transport.\n- Performance gates for tables/logs/metrics/heavy engines/loading fallbacks keep `DataTable` skeleton rows, log append bounds, `MetricTable`/relationship table alternatives, dynamic heavy-engine fallbacks, and reduced-motion/data-quality states.\n\n## Phase 13 status\n\nPhase 13 complete for UIKIT v1 release readiness:\n\n- TASK-13-01 component DoD complete: the component inventory marks each item complete for purpose, use, prohibited use, anatomy, variants, props, slots, events, states, normalized model boundary, permission boundary, examples, keyboard/focus and accessible role/name/state evidence, light/dark/long-content/responsive/material-state evidence, and performance evidence where applicable.\n- TASK-13-02 external artifacts complete: package READMEs, component inventory, token sheet, dependency decision register, preview route, accessibility/visual evidence archive, migration notes, spec traceability matrix, confirmation dependency register, performance reports, and release-readiness report are stored outside `specifications/uikit-v1/`.\n- TASK-13-03 final readiness review: package boundary gate passed, React Native readiness is preserved through neutral tokens/core contracts, engine-independent public contracts are documented, unresolved confirmations are explicit release blockers, no hidden public-contract dependency on implementation engines remains, and product API transport remains application-owned.\n\n## Component contract notes\n\n### Purpose\n\nPrimitive components provide the reusable Web React foundation for higher-order UIKIT surfaces while preserving normalized models, supplied permissions, semantic tokens, accessible names, keyboard focus, and safe state explanations.\n\n### Use\n\nUse these components for base controls, field composition, low-level selection, metadata display, and reusable loading/empty/error/permission/disconnected/partial/stale surfaces. Compose them in shell, table, form, governance, operation, and runtime components instead of creating local forks.\n\n### Prohibited use\n\nDo not pass raw backend responses, infer permissions from hidden data, embed product API calls, use hardcoded product colors, use emoji status icons as the only signal, or expose a lower-level engine such as Radix as the public product contract.\n\n### Anatomy\n\nEach primitive exposes a stable root element, semantic token classes, optional slots for labels, descriptions, icons, actions, errors, and children, plus `data-state` or permission attributes when state affects rendering.\n\n### Variants\n\nShared variants cover size (`sm`, `md`, `lg`), semantic tone (`neutral`, `info`, `success`, `warning`, `error`), action style (`primary`, `secondary`, `ghost`, `danger`), density through the provider, and state via `DataState` mappings.\n\n### Props and slots\n\nProps accept React children and primitive-specific values. Intent callbacks such as `onAction`, `onCopy`, and `onChange` expose user intent only; consuming applications own transport, persistence, audit, and server state.\n\n### Events\n\nEvents are local interaction events or intent callbacks. No primitive performs fetches, mutations, cache invalidation, or audit persistence directly.\n\n### State coverage\n\n`StateSurface` and feedback primitives cover loading, empty, partial, stale, error, unavailable, permission, disconnected, deleted, conflict, and pending-action presentations. `adaptPermissionState()` and `mapUxStateToDataState()` map blocked/denied to permission and degraded UX to partial, stale, unavailable, or a safe warning metadata surface.\n\n### Normalized model boundary\n\nPrimitives consume normalized core models such as `PermissionDecision`, `AsyncActionState`, `SafeUiError`, `ResourceRef`, and `FormValidationIssue`. Product-specific schemas are adapted before render by the consuming application.\n\n### Permission boundary\n\nComponents render disabled, omitted, or explanatory UI from supplied `PermissionDecision`. They do not infer access, fetch missing permission data, or render restricted content for later redaction.\n\n### Phase 4 layout and overlay boundary\n\nShell and navigation components consume normalized navigation/resource models (`NavItem`, `ResourceRef`, `PermissionDecision`) plus intent callbacks such as `onNavigate`, `onSearch`, and `onCommand`; they do not import or require a host router. Overlay components expose `open`/`onOpenChange` controlled state, trap user attention with dialog roles, restore focus when closed, and use dirty/pending guards to block unsafe close when supplied by the application. Mobile behavior uses overlay global navigation and full-width drawers, tablet behavior uses collapsible-width structures, and desktop behavior supports persistent navigation, dense toolbars, and standard drawers.\n\n## Evidence\n\n- `scripts/check-react-primitives.mjs` verifies Phase 3 exports and required documentation headings.\n- `scripts/check-react-shell.mjs` verifies Phase 4 shell/navigation/overlay exports, documentation, preview route, inventory, and traceability updates.\n- `scripts/check-react-tables.mjs` verifies Phase 5 tables/collections exports, controlled state, server-side intent markers, required-column protection, query examples, artifact updates, no product API transport, and representative 100-row performance.\n- `scripts/check-react-forms.mjs` verifies Phase 6 form/editing exports, React Hook Form/Zod/resolver dependencies, dirty/conflict/wizard accessibility markers, editing rules, preview examples, and evidence artifacts.\n- `scripts/check-react-governance.mjs` verifies Phase 7 governance/release exports, permission/redaction markers, approval and audit safeguards, visual-state markers, preview examples, and evidence artifacts.\n- `scripts/check-react-operations.mjs` verifies Phase 8 operations/visualization exports, engine-independent contracts, dynamic ECharts/@xyflow loading/fallback markers, table alternatives, data-quality/reduced motion evidence, no product API transport, and the 1000 samples across 10 series performance fixture.\n- `scripts/check-react-runtime.mjs` verifies Phase 9 technical/runtime exports, keyboard release, Monaco lazy fallback markers, log/terminal disconnected output preservation, permission/redaction/copy/export/download examples, no product API transport, and representative 100-line log frame append under 16ms where practical.\n- `scripts/check-react-application-runtime.mjs` verifies Phase 10 application runtime exports, business-language-first examples, accessible streaming, citation, artifact, feedback, retention-boundary, forbidden-history tests, permission, responsive markers, no product API transport, and state/intent callbacks only.\n- `scripts/check-react-compositions.mjs` verifies Phase 11 domain composition exports, all required composition domains, UF-001..UF-100 composition traceability, responsive markers, PermissionDecision filtering, no-local-fork policy, variants/slots/documented composition evidence, and no product API transport.\n- `scripts/check-react-cross-catalog-quality.mjs` verifies Phase 12 cross-catalog accessibility, responsive, security/permission/redaction, dangerous action, copy/export/download/terminal/code/payload/artifact/secret-adjacent, error, trace, citation, audit leakage, and performance gates for tables/logs/metrics/heavy engines/loading fallbacks.\n- `scripts/check-release-readiness.mjs` verifies Phase 13 UIKIT v1 release readiness, component DoD complete status, external artifacts complete status, package boundary gate passed evidence, React Native readiness, engine-independent public contracts, explicit release blockers for unresolved confirmations, and no hidden public-contract dependency on implementation engines.\n- `examples/preview/src/route.ts` records Phase 13 preview status and component families; `examples/preview/src/tables-query-example.ts` records TanStack Query adapter examples; `examples/preview/src/forms-editing-example.ts` records forms, dirty guard, conflict, wizard, review, and adapter examples; `examples/preview/src/governance-release-example.ts` records governance, approval, release, rollback, permission, redaction, and audit examples; `examples/preview/src/operations-visualization-example.ts` records operations, graph, chart, data-quality, reduced motion, and performance examples; `examples/preview/src/technical-runtime-example.ts` records technical runtime copy, export, download, permission, redaction, disconnection, keyboard, and Monaco lazy examples; `examples/preview/src/application-runtime-example.ts` records application runtime domain action, dynamic form, result, artifact, conversation, streaming, approval, run, feedback, channel, retention-boundary, and forbidden-history examples; `examples/preview/src/domain-composition-example.ts` records Phase 11 composition contracts, no-local-fork policy, and UF traceability.\n- `docs/uikit-v1/component-inventory.md`, `docs/uikit-v1/spec-traceability-matrix.md`, and `docs/uikit-v1/artifacts/release-readiness.md` track final acceptance status.\n\n## Source\n\nDerived from `platform/specifications/uikit-v1/SPEC.md`.\n","readmeFilename":"README.md","_rev":"1-9d7841c83c88fdd8afda1eb846066b3c"}