# WRNexus UI component inventory

This inventory maps the two approved v1.0 PDF checklists to implementation
stages. The source documents are **WRNexus Essential Component Inventory v1.0**
and **WRNexus Public SaaS Component System Checklist v1.0**.

## Release boundary

The current `@wrnexus/ui` catalog contains **891 real components**: the original
hand-tuned core plus the component-shaped inventory entries from both approved
PDFs. Repeated states, design checklist labels, content data models, analytics
events, SEO/head helpers, and non-rendering runtime helpers are intentionally not
body components.

SEO and structured data are intentionally handled by WRNexus page/head APIs.
Rendering them as body components would produce invalid or ineffective HTML.

## Coverage and specialization

The catalog now covers the prescribed families:

1. `design-tokens` and `icons`
2. `ui-forms`, `ui-calendar`, `ui-feedback`, `ui-overlays`
3. `ui-navigation`, `ui-data`, `ui-charts`, `ui-editors`, `ui-media`
4. `ui-shell`, `ui-marketing`, `ui-commerce`, `ui-developers`
5. `ui-content`, `ui-legal`, `ui-status`

Every catalog source compiles and shares semantic templates for forms, actions,
overlays, collections, feedback, visualizations, layouts, and content. These
templates provide responsive structure, theme tokens, motion, focus treatment,
disabled/loading/error props where relevant, semantic elements, and slots for
application content. Domain-specific logic (for example chart rendering, maps,
payments, CAPTCHA providers, or rich-text engines) remains application/provider
integration supplied through those slots rather than a hidden package dependency.

`packages/ui/component-reference.json` and `packages/ui/COMPONENTS.md` are
generated from the actual sources and are the authoritative prop reference.