@xemahq/ui-kernel 0.25.0 → 0.25.1

package/README.md

@@ -1,49 +1,15 @@
-<p align="center">
-<svg width="680" height="120" viewBox="0 0 680 120" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="@xemahq/ui-kernel">
-  <rect width="680" height="120" rx="14" fill="#0B1020"/>
-  <g transform="translate(28,34)">
-    <path d="M26 0 L52 15 L52 45 L26 60 L0 45 L0 15 Z" fill="#8B5CF6" opacity="0.18"/>
-    <path d="M26 12 L41 21 L41 39 L26 48 L11 39 L11 21 Z" fill="#8B5CF6"/>
-  </g>
-  <text x="92" y="52" font-family="ui-monospace,SFMono-Regular,Menlo,monospace" font-size="22" fill="#F8FAFC" font-weight="700">@xemahq/ui-kernel</text>
-  <text x="92" y="80" font-family="ui-sans-serif,system-ui,sans-serif" font-size="15" fill="#94A3B8">Host-agnostic UI kernel for the Xema frontend</text>
-  <text x="652" y="105" text-anchor="end" font-family="ui-sans-serif,system-ui,sans-serif" font-size="12" fill="#475569">xema.dev</text>
-</svg>
-</p>
-
-<p align="center">
-  <a href="https://xema.dev">Website</a> &middot;
-  <a href="https://www.npmjs.com/package/@xemahq/ui-kernel">npm</a>
-</p>
-
-<p align="center">
-  <img alt="npm" src="https://img.shields.io/npm/v/%40xemahq%2Fui-kernel?color=2563eb&label=npm">
-  <img alt="license" src="https://img.shields.io/npm/l/%40xemahq%2Fui-kernel?color=10b981">
-  <img alt="types" src="https://img.shields.io/npm/types/%40xemahq%2Fui-kernel?color=3178c6">
-</p>
-
 # @xemahq/ui-kernel
 
 > Host-agnostic UI kernel for the Xema frontend
 
 ## Overview
 
-The host-framework-agnostic UI kernel every frontend biome composes against. It
-defines the system bus — the orchestration contract for capability invocation,
-cross-biome intents, the command palette, deeplinks, and window management — and
-the biome-host contract surface, including the frontend-biome and host-bridge
-shapes, the singleton biome registry, and session contributions. React is the
-shared component model, but the kernel carries no router, bundler, or
-host-specific wiring; concrete host adapters live in separate packages. The
-system bus is pure orchestration — it never authorizes; policy is enforced by
-the backend.
+The host-agnostic UI kernel that Xema frontend biomes are built on. It provides `defineWebBiome` for declaring pages, the biome registry, the system bus for capability invocation, intents, the command palette and deeplinks, and the shared design system under `@xemahq/ui-kernel/ui`. The bus only orchestrates; the backend enforces policy.
 
 ## When to use it
 
-- Use it to author a frontend biome against the shared host contracts and
-  register it with the biome registry.
-- Reach for the system bus to dispatch capability invocations, intents, or
-  deeplinks across biomes.
+- You are authoring a frontend biome and registering it with the host.
+- You need the shared components so a biome looks identical to built-in ones.
 
 ## Installation
 
@@ -53,10 +19,6 @@ pnpm add @xemahq/ui-kernel
 
 ## Usage
 
-Author a web biome with `defineWebBiome` — a declarative page list where each
-`slug` single-sources both the nav route and the route path, and each page
-declares its menu `category` (the host owns where that category renders):
-
 ```tsx
 import { defineWebBiome } from '@xemahq/ui-kernel';
 import { Layers } from 'lucide-react';
@@ -76,45 +38,24 @@ export default defineWebBiome({
 });
 ```
 
-The helper emits the nav item + route (wrapping the lazily-loaded page in a
-`<Suspense>` boundary) and passes through `init`/`panels`/`session` for bespoke
-biomes. Pass a per-page `id` to keep a short nav id distinct from the route
-slug, or `navHidden: true` to register a route with no nav item.
+Each page's `slug` sets both its nav route and its path. Use a per-page `id` for a short nav id, or `navHidden: true` for a route with no nav item.
 
-Lower-level building blocks are also exported:
+Lower-level pieces:
 
 ```ts
 import { buildSystemBus, biomeRegistry } from '@xemahq/ui-kernel';
 
 const bus = buildSystemBus(hostPorts);
-
-// Register a frontend biome so the host can render its contributions:
 biomeRegistry.registerBiome(myBiome);
 ```
 
-## UI components
-
-Build your pages with the shared design system from `@xemahq/ui-kernel/ui` so a
-third-party biome renders pixel-identical to a built-in one (they resolve
-against the host theme at render):
-
-```tsx
-import {
-  Button, Badge, Input, Select, Dialog, Card, Tabs, Table, // primitives
-  PageShell, PageHeader, EmptyState, ErrorCard, StateCard, LoadingState, AsyncBoundary,
-  StatusBadge, ScopeBadge, ConfirmDeleteDialog, FormStepper, AsyncCombobox,
-  getStatusStyle, cn,
-} from '@xemahq/ui-kernel/ui';
-```
-
-Host-service hooks (toast, error copy, URL-backed page state) come from the
-`HostBridge` — e.g. `useMutationWithErrorToast`, `usePageState` from
-`@xemahq/ui-kernel` — so biomes never import host internals directly.
+Components come from `@xemahq/ui-kernel/ui` (for example `Button`, `Card`, `Table`, `PageShell`). Host hooks such as `useMutationWithErrorToast` and `usePageState` come from `@xemahq/ui-kernel`.
 
 ## Peer requirements
 
-- `react` — the shared component model.
-- `@tanstack/react-query` — async state for host data hooks.
+- `react` `^18.3.1`
+- `@tanstack/react-query` `^5.0.0`
+- `@xemahq/contracts` `>=0.4.0`
 
 ## License
 

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@xemahq/ui-kernel",
-  "version": "0.25.0",
+  "version": "0.25.1",
   "type": "module",
   "sideEffects": false,
-  "description": "Host-framework-agnostic UI kernel for the Xema OS. Defines the SystemBus orchestration contract (capability.invoke, cross-biome intents, command palette, xema:// deeplinks, window manager) AND the biome-host contract surface (FrontendBiome/FrontendBiomeFactory, HostBridge, the singleton biomeRegistry, session contributions) that every frontend biome composes against. No Vite, Next.js, or React-Router — React itself IS allowed as the shared component model (the contracts traffic in ReactNode/ComponentType and a React context). Concrete host adapters (router/auth/toast wiring) live in separate packages that consume this kernel. The SystemBus is pure orchestration: it never authorizes, the backend capability-router enforces all policy.",
+  "description": "Host-framework-agnostic UI kernel for Xema. Defines the SystemBus orchestration contract (capability.invoke, cross-biome intents, command palette, xema:// deeplinks, window manager) AND the biome-host contract surface (FrontendBiome/FrontendBiomeFactory, HostBridge, the singleton biomeRegistry, session contributions) that every frontend biome composes against. No Vite, Next.js, or React-Router — React itself IS allowed as the shared component model (the contracts traffic in ReactNode/ComponentType and a React context). Concrete host adapters (router/auth/toast wiring) live in separate packages that consume this kernel. The SystemBus is pure orchestration: it never authorizes, the backend capability-router enforces all policy.",
   "keywords": [
     "xema",
     "xema-platform",
@@ -50,7 +50,7 @@
     "@radix-ui/react-switch": "^1.2.5",
     "@radix-ui/react-tabs": "^1.1.12",
     "@radix-ui/react-tooltip": "^1.2.7",
-    "@xemahq/registry": "^0.1.4",
+    "@xemahq/registry": "^0.1.7",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "lucide-react": "^0.462.0",
@@ -74,14 +74,14 @@
     "@types/node": "25.2.3",
     "@types/react": "^18.3.30",
     "@types/react-dom": "^18.3.7",
-    "@xemahq/contracts": "^0.75.0",
+    "@xemahq/contracts": "^0.79.0",
     "eslint": "^9.39.4",
     "prettier": "3.6.2",
     "react": "^18.3.1",
     "react-dom": "^18.3.1",
     "typescript": "5.9.3",
     "vitest": "^3.2.4",
-    "@xemahq/eslint-config": "0.13.0"
+    "@xemahq/eslint-config": "0.14.0"
   },
   "exports": {
     ".": {
@@ -119,6 +119,6 @@
     "typecheck": "tsc -p tsconfig.lint.json --noEmit"
   },
   "xemaRelease": {
-    "sourceDigest": "sha256:532fe368e3a30f6d1ba2a687296d7fc7143e1d7f6fe21e8f0591db7d8a8a50ed"
+    "sourceDigest": "sha256:5a2f772fbd3db90cf259986714ab70187641c76c164abcaf315852b181235921"
   }
 }