release: complete UI component catalog 0.2.58

docs/UI-COMPONENT-INVENTORY.md

@@ -6,19 +6,18 @@ and **WRNexus Public SaaS Component System Checklist v1.0**.
 
 ## Release boundary
 
-The current `@wrnexus/ui` release targets the documents' combined **minimum
-first-release component set** and **essential components to build first**. These
-are implemented as real components with theme tokens, responsive rules,
-keyboard-native controls, visible focus, reduced-motion handling, and mobile
-touch targets—not name-only aliases.
+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.
 
-## Subsequent staged packages
+## Coverage and specialization
 
-The remaining expanded inventory is retained for staged implementation in the
-dependency order prescribed by the PDFs:
+The catalog now covers the prescribed families:
 
 1. `design-tokens` and `icons`
 2. `ui-forms`, `ui-calendar`, `ui-feedback`, `ui-overlays`
@@ -26,6 +25,13 @@ dependency order prescribed by the PDFs:
 4. `ui-shell`, `ui-marketing`, `ui-commerce`, `ui-developers`
 5. `ui-content`, `ui-legal`, `ui-status`
 
-Each stage must satisfy rendering, keyboard, focus, semantics, disabled/loading
-states, mobile layout from 320 px, light/dark themes, reduced motion, no
-horizontal overflow, documentation, and production-build tests before release.
+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.