@lifeonlars/prime-yggdrasil 0.2.5 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeonlars/prime-yggdrasil",
-  "version": "0.2.5",
+  "version": "0.3.0",
   "type": "module",
   "description": "AI-agent-friendly PrimeReact design system for component-driven development with semantic tokens and dark mode support",
   "keywords": [
@@ -39,9 +39,14 @@
     "./typography.css": "./dist/typography.css",
     "./docs/*": "./docs/*"
   },
+  "bin": {
+    "yggdrasil": "./cli/bin/yggdrasil.js"
+  },
   "files": [
     "dist",
     "docs",
+    "cli",
+    ".ai",
     "README.md",
     "LICENSE"
   ],

package/docs/Fixes.md

@@ -1,258 +0,0 @@
-# Prime Yggdrasil npm Package Issues - Testing Report
-
-## Version History
-
-### v0.1.1 - Initial Test
-
-**Status:** ❌ BROKEN - Missing 4 critical CSS files
-
-### v0.1.2 - After First Fix
-
-**Status:** ⚠️ PARTIALLY FIXED - Missing 1 critical file (prime-palette.css)
-
-### v0.1.3 - After Second Fix
-
-**Status:** ❌ BROKEN - CSS syntax error in misc.css
-
----
-
-## Issue #1: Missing CSS Files (v0.1.1) ✅ RESOLVED
-
-### Problem
-
-The `yggdrasil-light.css` and `yggdrasil-dark.css` files contain `@import` statements that reference CSS files that don't exist in the published package.
-
-**Status:** ✅ FIXED in v0.1.2
-
----
-
-## Issue #2: Missing prime-palette.css (v0.1.2) ✅ RESOLVED
-
-### Problem
-
-Both `semantic-light.css` and `semantic-dark.css` import `prime-palette.css` which didn't exist in dist folder.
-
-**Status:** ✅ FIXED in v0.1.3 - File is now present (8.1KB)
-
----
-
-## Issue #3: CSS Syntax Error in misc.css (v0.1.3) ❌ CURRENT ISSUE
-
-### Problem (NEW in v0.1.3)
-
-The file `dist/components/misc.css` has a CSS syntax error - an extra closing brace `}` at line 606.
-
-**Build Error:**
-
-```
-[vite:css] [postcss] postcss-import:
-S:\...\dist\components\misc.css:606:1: Unexpected }
-```
-
-**Location:** `components/misc.css` line 606
-
-**Analysis:**
-
-- Lines 1-606 contain:
-  - **Opening braces:** 127
-  - **Closing braces:** 128
-  - **Extra closing braces:** 1
-
-**Context around line 606:**
-
-```css
-  .border-round-right-lg {
-    border-top-right-radius: var(--radius-lg) !important;
-    border-bottom-right-radius: var(--radius-lg) !important;
-  }
-}  ← Line 606: EXTRA CLOSING BRACE
-
-  .p-inplace .p-inplace-display {
-    padding: 0.75rem 0.75rem;
-```
-
-**Impact:**
-
-- ❌ Production build fails completely
-- ❌ Cannot deploy application
-- ❌ PostCSS parsing error prevents CSS compilation
-
-**Root Cause:**
-There's an unmatched closing brace at line 606. This appears to be a leftover from editing or a merge conflict. The brace doesn't close any open block.
-
----
-
-## Recommended Fix for v0.1.4
-
-### Fix: Remove Extra Closing Brace
-
-**In `dist/components/misc.css` line 606:**
-
-```diff
-  .border-round-right-lg {
-    border-top-right-radius: var(--radius-lg) !important;
-    border-bottom-right-radius: var(--radius-lg) !important;
-  }
-- }
-
-  .p-inplace .p-inplace-display {
-    padding: 0.75rem 0.75rem;
-```
-
-**OR** - Check the source file before build:
-
-If this error is coming from the source, fix it in the source file (likely `src/theme/components/misc.css` or similar) and rebuild.
-
-### Validation Step
-
-After fixing, validate the CSS:
-
-```bash
-# Count braces - should be equal
-grep -c "{" dist/components/misc.css
-grep -c "}" dist/components/misc.css
-
-# OR use a CSS linter
-npx stylelint dist/components/misc.css
-```
-
----
-
-## Files Status in v0.1.3
-
-All required files are now present:
-
-- ✅ `components.css` (469 bytes)
-- ✅ `foundations.css` (6.1KB)
-- ✅ `prime-palette.css` (8.1KB) - **FIXED in v0.1.3**
-- ✅ `radius.css` (1.6KB)
-- ✅ `semantic-dark.css` (9.0KB)
-- ✅ `semantic-light.css` (8.8KB)
-- ✅ `yggdrasil-dark.css` (399 bytes)
-- ✅ `yggdrasil-light.css` (401 bytes)
-- ✅ `components/` directory with individual component CSS files
-  - ❌ `components/misc.css` has syntax error
-
----
-
-## Testing Checklist for v0.1.4
-
-When the package is updated, verify:
-
-- [ ] Remove extra closing brace from misc.css line 606
-- [ ] CSS linting passes (`npx stylelint dist/**/*.css`)
-- [ ] Brace count matches (opening === closing)
-- [ ] `npm run build` succeeds in consumer project
-- [ ] No PostCSS parsing errors
-- [ ] `yggdrasil-light.css` loads without errors
-- [ ] `yggdrasil-dark.css` loads without errors
-- [ ] All semantic tokens available in browser
-- [ ] Production build succeeds
-- [ ] Dark mode switching works
-
----
-
-## Test Commands
-
-To reproduce the issue in v0.1.3:
-
-```bash
-# Install the package
-npm install @lifeonlars/prime-yggdrasil@0.1.3
-
-# Import in your app (src/main.tsx)
-import '@lifeonlars/prime-yggdrasil/yggdrasil-light.css'
-
-# Try to build
-npm run build
-
-# Expected error:
-# [postcss] postcss-import: ...misc.css:606:1: Unexpected }
-```
-
----
-
-## Progress Summary
-
-### v0.1.1 → v0.1.2
-
-✅ **Fixed:** Added 4 missing CSS files
-
-- radius.css
-- semantic-light.css
-- semantic-dark.css
-- components.css
-
-### v0.1.2 → v0.1.3
-
-✅ **Fixed:** Added prime-palette.css (8.1KB)
-❌ **New Issue:** CSS syntax error in components/misc.css
-
-### v0.1.3 → v0.1.4 (Required)
-
-❌ **Remaining Issue:** Extra closing brace in misc.css line 606
-
-- Single character fix
-- Blocking all production builds
-
----
-
-## Additional Notes
-
-### Good Progress Overall!
-
-- v0.1.2: Fixed the main missing files issue
-- v0.1.3: Fixed the nested import issue (prime-palette.css)
-- **Remaining:** Just one syntax error (extra `}` character)
-
-### Build Process Recommendations
-
-To prevent CSS syntax errors in future releases:
-
-1. **Add CSS Linting to CI/CD:**
-
-   ```json
-   {
-     "scripts": {
-       "lint:css": "stylelint \"dist/**/*.css\"",
-       "test:css": "postcss dist/**/*.css --syntax postcss"
-     }
-   }
-   ```
-
-2. **Validate Build Output:**
-
-   ```bash
-   # After build, before publish
-   npm run lint:css
-   npm run test:css
-   ```
-
-3. **Test in Consumer Project:**
-   ```bash
-   # Link locally and test build
-   npm link
-   cd ../test-project
-   npm link @lifeonlars/prime-yggdrasil
-   npm run build
-   ```
-
-### CSS File Generation
-
-The misc.css file is likely generated from source. Check:
-
-- Is there a build script that concatenates CSS files?
-- Is there a template or generator that might have introduced the extra brace?
-- Did a recent merge introduce the syntax error?
-
----
-
-## Quick Fix Summary
-
-**The fix is simple - just remove one character:**
-
-**File:** `dist/components/misc.css`
-**Line:** 606
-**Action:** Delete the standalone `}` on this line
-
-After this fix, the package should work correctly! ✨

package/docs/archive/README.md

@@ -1,27 +0,0 @@
-# Documentation Archive
-
-This folder contains outdated or superseded documentation kept for historical reference.
-
-## Archived Files
-
-### SEMANTIC-MIGRATION-PLAN.md
-**Status**: ✅ Completed
-**Date Archived**: 2026-01-05
-**Reason**: Migration successfully completed. 727 colors replaced with semantic tokens (96% coverage).
-**Superseded By**: Work is complete, no replacement doc needed.
-
----
-
-Files in this directory are kept for reference only and should not be used for current development.
-
-### YGGDRASIL_THEME.md
-**Status**: ⚠️ Superseded
-**Date Archived**: 2026-01-05
-**Reason**: Outdated theme documentation from early project stage.
-**Superseded By**: `src/theme/README.md` and `docs/README.md`
-
-### agentic_policy.md  
-**Status**: ⚠️ Superseded
-**Date Archived**: 2026-01-05
-**Reason**: Early agentic development policy, now replaced with comprehensive guide.
-**Superseded By**: `docs/AI-AGENT-GUIDE.md`

package/docs/archive/SEMANTIC-MIGRATION-PLAN.md

@@ -1,177 +0,0 @@
-# Semantic Token Migration Plan
-
-**Generated:** 2026-01-04
-**Status:** In Progress
-**Total Hardcoded Colors:** 755
-**Components Affected:** 67
-
-## Migration Strategy
-
-### Phase 1: High-Impact Components (Priority)
-Components with most hardcoded colors that are commonly used:
-
-1. **Button** (72 colors) - ⚠️ CRITICAL - Most used component
-2. **DataTable** (32 colors) - ⚠️ HIGH - Complex data display
-3. **Menu Components** (166 colors total across 6 menu types)
-   - Menubar (49)
-   - Megamenu (47)
-   - Menu (20)
-   - Slidemenu (20)
-   - Tieredmenu (19)
-   - Contextmenu (17)
-
-### Phase 2: Form & Input Components
-4. **Dropdown/Select Components** (31 colors)
-   - TreeSelect (19)
-   - CascadeSelect (12)
-5. **Lists & Selection** (46 colors)
-   - Listbox (16)
-   - OrderList (16)
-   - PickList (14)
-6. **Date/Time** (22 colors)
-   - DatePicker (22)
-7. **Autocomplete** (8 colors)
-
-### Phase 3: Navigation & Layout
-8. **Accordion** (15 colors)
-9. **TabView** (13 colors)
-10. **Panel Components** (22 colors)
-    - Panel (12)
-    - Fieldset (10)
-11. **Stepper** (12 colors)
-12. **TabMenu** (10 colors)
-13. **Breadcrumb** (7 colors)
-
-### Phase 4: Data Display
-14. **TreeTable** (28 colors)
-15. **Tree** (13 colors)
-16. **DataView** (8 colors)
-17. **DataScroller** (9 colors)
-18. **Galleria** (9 colors)
-19. **Carousel** (5 colors)
-20. **Timeline** (2 colors)
-
-### Phase 5: Misc Components
-21. **SplitButton** (23 colors)
-22. **PanelMenu** (30 colors)
-23. **OrganizationChart** (11 colors)
-24. **ToggleButton** (13 colors)
-25. **OverlayPanel** (8 colors)
-26. **Remaining** (< 10 colors each)
-
-## Required Semantic Tokens
-
-Based on analysis, we need to ensure these semantic tokens exist:
-
-### Button Variants
-- `--button-primary-background`
-- `--button-primary-text`
-- `--button-primary-border`
-- `--button-primary-hover-background`
-- `--button-primary-active-background`
-- `--button-secondary-*` (full set)
-- `--button-help-*` (full set - purple variant)
-- `--button-contrast-*` (full set - dark variant)
-- `--button-outlined-*` (full set)
-- `--button-text-*` (full set)
-
-### Menu/Navigation
-- `--menu-background`
-- `--menu-item-background`
-- `--menu-item-hover-background`
-- `--menu-item-active-background`
-- `--menu-text-default`
-- `--menu-text-hover`
-- `--menu-separator-border`
-
-### Data Display
-- `--table-header-background`
-- `--table-header-text`
-- `--table-row-background`
-- `--table-row-alt-background` (striping)
-- `--table-row-hover-background`
-- `--table-row-selected-background`
-- `--table-cell-border`
-
-### Form Controls (extend existing)
-- Need to verify all input states are covered
-- Add any missing variant tokens
-
-## Migration Workflow
-
-### For Each Component:
-
-1. **Analyze** - Review hardcoded colors in context
-2. **Map** - Create semantic token mappings
-3. **Add Tokens** - Add any missing tokens to both semantic-light.css and semantic-dark.css
-4. **Replace** - Use targeted replacement script
-5. **Test** - Verify in Storybook (light + dark)
-6. **Contrast** - Run APCA tests for new tokens
-7. **Document** - Update if new token categories added
-
-### Example: Button Migration
-
-```css
-/* BEFORE */
-.p-button {
-  background: #3b82f6;
-  color: #ffffff;
-}
-
-/* AFTER */
-.p-button {
-  background: var(--button-primary-background);
-  color: var(--button-primary-text);
-}
-```
-
-## Current Status
-
-### ✅ Completed Components
-- Dialog
-- Checkbox
-- RadioButton
-- Card (partial - uses semantic tokens)
-
-### 🚧 In Progress
-- None currently
-
-### 📋 Next Up
-1. Button (highest priority)
-2. Menu components (second highest)
-3. DataTable
-
-## Token Addition Checklist
-
-When adding new semantic tokens:
-
-1. ☐ Add to `semantic-light.css`
-2. ☐ Add to `semantic-dark.css`
-3. ☐ Test contrast (APCA)
-4. ☐ Document in theme README if new category
-5. ☐ Update this migration plan
-
-## Estimated Completion
-
-- **Phase 1:** 3-4 sessions (~270 colors)
-- **Phase 2:** 2-3 sessions (~107 colors)
-- **Phase 3:** 2 sessions (~79 colors)
-- **Phase 4:** 2 sessions (~89 colors)
-- **Phase 5:** 2-3 sessions (~210 colors)
-
-**Total:** 11-15 focused sessions
-
-## Success Metrics
-
-- ✅ All 755 hardcoded colors replaced
-- ✅ 100% APCA contrast pass rate maintained
-- ✅ Full dark mode support for all components
-- ✅ Consistent theming across component library
-
-## Notes for AI Agents
-
-- Always work on one component at a time
-- Test thoroughly in both themes before moving on
-- Maintain contrast requirements
-- Follow existing naming patterns for tokens
-- Update this document after each component completion