@nadicodeai/ui 0.19.2 → 0.20.0

package/AGENTS.md

@@ -29,5 +29,5 @@ The `@nadicodeai/ui` npm workspace: the shared NadicodeAI React UI package on br
 | Website page assembly | `../../website/AGENTS.md` |
 | Portal screens | `../../portal/AGENTS.md` |
 | User-visible UI work | `../../skills/nadicodeai-product-design/SKILL.md`, loaded after this rulebook |
-| Product-component consumption order and TUI semantics | `docs/migration/nadia-consumer-readiness.md`, `docs/terminal-tui-semantics.md` |
+| TUI semantics | `docs/terminal-tui-semantics.md` |
 | Docs shipped to package consumers | `docs/contract.md` owns invariants, `docs/consuming-cross-repo.md` owns setup, and `llms.txt`, `docs/agents/nadicodeai-ui.md`, `docs/migration/`, and `skills/nadicodeai-ui/SKILL.md` map to those owners while documenting their own component or workflow surface |

package/README.md

@@ -177,8 +177,6 @@ The npm package includes agent-facing files on purpose. Agents should read:
 - `docs/contract.md` for the package contract
 - `llms.txt` for a concise import/setup index
 - `docs/agents/nadicodeai-ui.md` for detailed usage and maintenance guidance
-- `docs/migration/nadia-consumer-readiness.md` for consumer migration order
-  and readiness gates
 - `skills/nadicodeai-ui/SKILL.md` when the agent runtime supports skills
 
 These files are packaged through npm `files`; they are not runtime module

package/docs/agents/nadicodeai-ui.md

@@ -24,8 +24,6 @@ in agent prose. Follow the owning source or document above.
 - Product compositions and sections:
   [`../product-compositions.md`](../product-compositions.md) and
   [`../product-sections.md`](../product-sections.md).
-- Consumer order, fixture redaction, and readiness gates:
-  [`../migration/nadia-consumer-readiness.md`](../migration/nadia-consumer-readiness.md).
 - Terminal and TUI semantics:
   [`../terminal-tui-semantics.md`](../terminal-tui-semantics.md).
 

package/docs/consuming-cross-repo.md

@@ -42,9 +42,14 @@ partials beside it. The package declares its own built component sources; Tailwi
 normal automatic detection covers the consumer application. The app still owns
 its PostCSS configuration, theme provider, and persisted mode preference.
 
-If the app needs bundled Geist files rather than its framework's font loader,
-that asset import is one of the intentional direct-API cases described above.
-Font loading is an asset decision, not a second design stylesheet.
+That stylesheet also delivers the brand typeface. The design-system CSS module
+declares the `@font-face` rules for Geist and Geist Mono and loads the packaged
+woff2 files, so a consuming app must not add its own font loader for those two
+families. A framework loader on top registers a second, differently sourced face
+for the same family names, which downloads the fonts twice and leaves no defined
+winner. Import files under `@nadicodeai/design-system/assets/fonts/*` only when
+the consumer wants the faces without the CSS module; that is one of the
+intentional direct-API cases described above.
 
 ## NadicodeAI logo
 

package/docs/contract.md

@@ -38,7 +38,7 @@ The source tree, barrels, and package exports own the current reusable section v
 
 ## Consumer Boundary
 
-Consumers own routing, auth, app data, server actions, runtime adapters, permission decisions, analytics, and app-specific copy. The package owns the presentational structure and state vocabulary only. [`migration/nadia-consumer-readiness.md`](migration/nadia-consumer-readiness.md) owns migration order and readiness; [`terminal-tui-semantics.md`](terminal-tui-semantics.md) owns TUI semantics.
+Consumers own routing, auth, app data, server actions, runtime adapters, permission decisions, analytics, and app-specific copy. The package owns the presentational structure and state vocabulary only. [`terminal-tui-semantics.md`](terminal-tui-semantics.md) owns TUI semantics.
 
 App source composes layout, data, behavior, and semantic content around package components. It does not restyle an imported component root: appearance changes enter through the component's typed variant or are added to the owning package component. App `className` values on package components are limited to structural layout and sizing. App source uses semantic roles such as `bg-background` and `text-foreground`; raw Tailwind palette colors and canonical `nc-*` color utilities stay behind package-owned primitives such as `BrandField`. Visible controls come from `@nadicodeai/ui`, while hidden inputs remain valid form transport. The root ESLint rules `nadicodeai/no-shadcn-appearance-override`, `nadicodeai/no-raw-color-utility`, and `nadicodeai/no-native-visible-control` enforce this boundary.
 

package/llms.txt

@@ -15,7 +15,6 @@ Use this file as a map; read the owning document before changing behavior.
 - Agent work surfaces: `docs/agent-work-surfaces.md`.
 - Product compositions and sections: `docs/product-compositions.md` and
   `docs/product-sections.md`.
-- Consumer migration: `docs/migration/nadia-consumer-readiness.md`.
 - Terminal and TUI semantics: `docs/terminal-tui-semantics.md`.
 - Maintenance workflow and live shadcn or AI Elements discovery:
   `docs/agents/nadicodeai-ui.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/ui",
-  "version": "0.19.2",
+  "version": "0.20.0",
   "type": "module",
   "publishConfig": {
     "access": "public"
@@ -63,7 +63,7 @@
   },
   "dependencies": {
     "@base-ui/react": "^1.6.0",
-    "@nadicodeai/design-system": "0.19.2",
+    "@nadicodeai/design-system": "0.20.0",
     "@rive-app/react-webgl2": "^4.29.1",
     "@streamdown/cjk": "^1.0.3",
     "@streamdown/code": "^1.1.1",

package/skills/nadicodeai-ui/SKILL.md

@@ -49,7 +49,7 @@ import { AgentChat } from "@nadicodeai/ui/components/agent-chat";
 - Use package product components for shared settings, shell, installer, plugin-boundary, agent chat, artifact, file, diff, and redacted terminal summary UI.
 - Use first-party shadcn registry source in the consuming app for generic data tables, command palettes, and chart cards; do not import a NadicodeAI package abstraction for those patterns.
 - Keep routes, data, auth, server actions, persistence, permission decisions, runtime adapters, analytics, and product-specific copy in the consuming app.
-- Follow `docs/migration/nadia-consumer-readiness.md`: web admin or portal first, installer second, desktop shell third, desktop chat last, TUI through `docs/terminal-tui-semantics.md`.
+- Render TUI surfaces through `docs/terminal-tui-semantics.md`.
 - Fixtures must be synthetic or redacted and cover provider, model, plugin, approval, diff, terminal, installer recovery, queued, streaming, and interrupted states. Do not use generic SaaS/card-grid filler, secrets, environment values, raw terminal output, hidden reasoning, user memory, fake customers, or fake proof metrics.
 
 ## Forms

package/docs/migration/nadia-consumer-readiness.md

@@ -1,180 +0,0 @@
-# Nadia Consumer Readiness
-
-This guide records the first consumer-readiness path for shared Nadia product UI.
-The components are presentational package surface. Consuming apps still own
-routes, auth, data loading, mutations, persistence, runtime adapters, permission
-decisions, analytics, and product-specific copy.
-
-## Required Setup
-
-Complete [`../consuming-cross-repo.md`](../consuming-cross-repo.md) before
-starting a migration; it owns consumer setup. Component styling must satisfy
-[`../contract.md`](../contract.md).
-
-Use public package subpaths:
-
-```tsx
-import { DashboardShell } from "@nadicodeai/ui/components/dashboard-shell";
-import { AgentChat } from "@nadicodeai/ui/components/agent-chat";
-```
-
-Use first-party shadcn registry source directly in the consuming app for generic
-data tables, command palettes, and chart cards. Do not migrate those patterns
-through a NadicodeAI package wrapper.
-
-## Consumer Mapping
-
-### Toast
-
-The imperative toast API is package-owned. Import it from the
-`@nadicodeai/ui/components/toast` subpath, and mount `<Toaster />` from
-`@nadicodeai/ui/components/sonner` once at the app root.
-
-```tsx
-import { toast } from "@nadicodeai/ui/components/toast";
-
-showToast(message, "success"); // → toast.success(message)
-showToast(message, "error"); //   → toast.error(message)
-```
-
-Per-toast duration is a sonner option passed as the second argument.
-Consumers must not depend on `sonner` directly.
-
-### Confirm flows
-
-`ConfirmDialog` from `@nadicodeai/ui/components/confirm-dialog` takes `open`,
-`onConfirm`, `onCancel`, `title`, and optional `description`, `confirmLabel`,
-`cancelLabel`, `destructive`, `loading`. `useConfirmAction` from
-`@nadicodeai/ui/hooks` replaces bespoke delete-confirm hooks:
-
-```tsx
-useConfirmAction({ onConfirm }); // (value) => Promise<void> | void
-// → { request, cancel, confirm, isBusy, isOpen, pending }
-```
-
-| Old (`useConfirmDelete`) | New (`useConfirmAction`) |
-| --- | --- |
-| `onDelete` | `onConfirm` |
-| `requestDelete` | `request` |
-| `isDeleting` | `isBusy` |
-| `pendingId` | `pending` |
-
-A throw inside `onConfirm` keeps the dialog open and the hook swallows it —
-surface errors from inside `onConfirm` yourself, with a toast or an inline
-alert. Non-delete confirms (restart, reset, reload) use the same component
-with either plain boolean state or the same hook.
-
-### Typography
-
-The package ships no `Text`/`Heading` component — the same boundary that
-keeps `DataTable` and `CommandPalette` out. The type scale is design-system
-CSS consumed as classes on raw elements: `nc-type-display-xl/lg/md/sm`,
-`nc-type-title-lg/md/sm`, `nc-type-body-lg/md/sm` (plus `-strong` variants
-for `body-md`/`body-sm`), `nc-type-caption` (plus `-strong` and `-mono`),
-`nc-type-code`, and `nc-type-button-md/lg`.
-
-| Old usage | New usage |
-| --- | --- |
-| Page-level heading | `<h1 className="nc-type-title-lg">` (or a `display-*` class at hero scale) |
-| Section header (the dominant H2 `variant="sm"` pattern) | `<h2 className="nc-type-title-sm">` |
-| Body copy | `<p className="nc-type-body-md">` |
-| Fine print / labels | `nc-type-caption` |
-| Code | `nc-type-code` |
-
-### Segmented control
-
-Single-select segmented UI is the existing `ToggleGroup`:
-
-```tsx
-<ToggleGroup spacing={0} variant="outline">
-  <ToggleGroupItem value="day">Day</ToggleGroupItem>
-  <ToggleGroupItem value="week">Week</ToggleGroupItem>
-</ToggleGroup>
-```
-
-Base UI's `ToggleGroup` is single-select by default (`toggleMultiple`
-defaults to `false`), and its value is an array. Controlled usage is
-`value={[current]}` with:
-
-```tsx
-onValueChange={(next) => {
-  if (next.length) setCurrent(next[0]);
-}}
-```
-
-The length guard preserves radio semantics by ignoring deselection of the
-active item. A label-plus-group row ("FilterGroup") is an app-level flex
-composition, not package surface.
-
-### Copy affordances
-
-Copy-to-clipboard UI is the AI Elements surface — a sanctioned public path.
-Use `Snippet`/`SnippetCopyButton` and `CodeBlockCopyButton` from
-`@nadicodeai/ui/ai-elements`.
-
-| Old | New |
-| --- | --- |
-| `CommandBlock(label, code)` | `Snippet` with `SnippetCopyButton` |
-| Bare `CopyButton(text)` | `SnippetCopyButton` inside a `Snippet`, or an app-local `Button` when no snippet chrome is wanted |
-
-### Breakpoints
-
-`useIsMobile()` (fixed 768) and `useBelowBreakpoint(px)` (true strictly below
-`px`) both ship from `@nadicodeai/ui/hooks`.
-
-## Migration Order
-
-1. Web admin or portal validation slice.
-2. Installer and bootstrap flows.
-3. Desktop shell and plugin boundary surfaces.
-4. Desktop chat and runtime work surfaces.
-5. TUI consumers through the terminal semantic mapping document.
-
-Desktop chat is last because it carries runtime-sensitive approval, streaming,
-queue, attachment, file, diff, and terminal states. Terminal consumers should
-mirror `docs/terminal-tui-semantics.md` instead of importing a DOM runtime.
-
-## Readiness Gates
-
-- The consumer satisfies the canonical setup in
-  [`../consuming-cross-repo.md`](../consuming-cross-repo.md).
-- Product components are imported from `@nadicodeai/ui/components/*` public
-  subpaths, not `src/*`.
-- At least one local shell, bento, settings, installer, plugin, or chat
-  layout responsibility is removed from the consumer.
-- Routes, data, auth, copy, persistence, and runtime behavior remain app-owned.
-- Fixtures use synthetic or redacted provider, model, plugin, approval, diff,
-  terminal, installer, and agent-work scenarios.
-- No fixture contains secrets, environment values, raw terminal output, hidden
-  reasoning, user memory, fake customers, fake proof metrics, or generic SaaS
-  filler.
-
-## First Validation Slice
-
-The in-repo portal is the first real consumer slice. It already imports package
-CSS at `portal/src/app/layout.tsx`. Its shell now consumes
-`@nadicodeai/ui/components/dashboard-shell` and keeps portal-owned route
-definitions, access checks, data, and Italian copy in `portal/`.
-
-This validates the package boundary because the shared component owns responsive
-dashboard chrome, mobile navigation trigger, content containment, and sidebar
-structure while the portal keeps the Nadia Agents activation domain.
-
-## Fixture Expectations
-
-Use NadicodeAI-relevant synthetic/redacted fixtures:
-
-- Data and settings: provider rows, model choices, plugin status, session state,
-  loading, permission, error, empty, and recovery copy.
-- Auth and installer: activation-shaped states, expired or invalid pairing,
-  retry and recovery actions, no live OTPs or secrets.
-- Shell and plugin: realistic navigation hierarchy, permission badges, disabled,
-  warning, error, unsafe, and contained-overflow states.
-- Agent, file, diff, and terminal: approval choices, tool failure, redacted
-  terminal summaries, changed-file hierarchy, interrupted, queued, and streaming
-  states.
-
-Brand and marketing components remain part of the same package surface. Consumer
-migrations should not hide or replace `PageFrame`, `SectionIntro`, `Bento`,
-`MediaMount`, `DemoSurface`, `HeroSplit`, `NavBar`, `Footer`, `BrandWordmark`,
-or the existing marketing sections.