@jmruthers/pace-core 0.6.4 → 0.6.6

package/docs/standards/ALIGNMENT_REVIEW_SUMMARY.md

@@ -0,0 +1,192 @@
+# Standards and Cursor Rules Alignment Review Summary
+
+**Date**: 2025-01-28  
+**Reviewer**: AI Assistant  
+**Status**: ✅ Complete
+
+## Overview
+
+This document summarizes the comprehensive review and alignment of standards documentation (`packages/core/docs/standards/`) and cursor rules (`packages/core/cursor-rules/`). The review ensured:
+
+1. ✅ Structure and naming alignment for traceability
+2. ✅ No contradictions between standards and rules
+3. ✅ No missing content in either standards or rules
+4. ✅ Cursor rules optimized for AI agents
+5. ✅ Consistent cross-references between standards and rules
+
+## Changes Made
+
+### 1. Fixed Broken References
+
+**Issue**: Standards README and 01-standards-compliance referenced non-existent files.
+
+**Fixed**:
+- Updated `packages/core/docs/standards/README.md` to remove references to non-existent consuming app standards
+- Updated `packages/core/docs/standards/01-standards-compliance.md` to reference actual standards files
+- Updated `packages/core/docs/standards/02-project-structure.md` to fix related documentation links
+
+### 2. Standardized Cross-References
+
+**Issue**: Inconsistent paths to cursor rules from standards files.
+
+**Fixed**:
+- Standardized all cursor rule references in standards to use `../../cursor-rules/` path
+- Added reverse links from all cursor rules to their corresponding standards
+- Used consistent format: `**📚 Human-Readable Standard**: See [XX-standard.md]...`
+
+### 3. Enhanced Cursor Rules for AI Optimization
+
+**Improvements**:
+- Added "Human-Readable Standard" links at the top of each cursor rule
+- Enhanced 08-markup-quality.mdc with critical CSS configuration warning
+- Added decision trees where appropriate (error handling, performance, CI/CD)
+- Improved AI agent instructions in rule headers
+
+### 4. Improved Traceability
+
+**Added**:
+- Consistent bidirectional links between standards and rules
+- Clear numbering alignment (00-12)
+- Reference sections in standards pointing to related standards
+- Reference sections in rules pointing to standards
+
+## Alignment Verification
+
+### Standards → Rules Mapping
+
+| Standard | Rule | Status | Notes |
+|----------|------|--------|-------|
+| 00-pace-core-compliance.md | 00-pace-core-compliance.mdc | ✅ Aligned | Both cover pace-core usage patterns |
+| 01-standards-compliance.md | 01-standards-compliance.mdc | ✅ Aligned | Meta-standard for precedence |
+| 02-project-structure.md | 02-project-structure.mdc | ✅ Aligned | Structure and organization |
+| 03-solid-principles.md | 03-solid-principles.mdc | ✅ Aligned | SOLID principles |
+| 04-testing-standards.md | 04-testing-standards.mdc | ✅ Aligned | Testing framework consistency |
+| 05-bug-reports-and-features.md | 05-bug-reports-and-features.mdc | ✅ Aligned | Issue reporting templates |
+| 06-code-quality.md | 06-code-quality.mdc | ✅ Aligned | Code quality standards |
+| 07-tech-stack-compliance.md | 07-tech-stack-compliance.mdc | ✅ Aligned | Tech stack requirements |
+| 08-markup-quality.md | 08-markup-quality.mdc | ✅ Aligned | Markup and CSS configuration |
+| 09-rbac-compliance.md | 09-rbac-compliance.mdc | ✅ Aligned | RBAC contract and RLS patterns |
+| 10-error-handling-patterns.md | 10-error-handling-patterns.mdc | ✅ Aligned | Error handling patterns |
+| 11-performance-optimization.md | 11-performance-optimization.mdc | ✅ Aligned | Performance best practices |
+| 12-ci-cd-integration.md | 12-ci-cd-integration.mdc | ✅ Aligned | CI/CD patterns |
+
+### Rules → Standards Mapping
+
+All 13 cursor rules (00-12) have corresponding standards. ✅ Complete
+
+## Contradictions Found and Resolved
+
+### None Found ✅
+
+After thorough review, no contradictions were found between standards and rules. The standards provide human-readable documentation, while the rules provide AI-optimized directives that align with the standards.
+
+## Gaps Identified
+
+### 1. CSS Configuration Emphasis
+
+**Issue**: The 08-markup-quality standard has extensive CSS configuration details, but the rule didn't emphasize this enough.
+
+**Resolution**: Added critical CSS configuration warning section at the top of 08-markup-quality.mdc rule with checklist and reference to standard.
+
+### 2. Missing Reverse Links
+
+**Issue**: Cursor rules didn't consistently link back to standards.
+
+**Resolution**: Added "Human-Readable Standard" links to all cursor rules.
+
+### 3. Broken References
+
+**Issue**: Some standards referenced non-existent files.
+
+**Resolution**: Fixed all broken references to point to actual standards files.
+
+## Recommendations for Future Enhancements
+
+### Potential New Standards/Rules
+
+While the current set is comprehensive, consider adding:
+
+1. **Security Patterns** (beyond RBAC/RLS)
+   - Input sanitization patterns
+   - XSS prevention
+   - CSRF protection
+   - Secure authentication flows
+
+2. **Database Migration Patterns**
+   - Migration naming conventions
+   - Rollback strategies
+   - Data migration best practices
+   - Migration testing patterns
+
+3. **API Design Patterns** (beyond RPC naming)
+   - API versioning strategies
+   - Rate limiting patterns
+   - Caching strategies for APIs
+   - API documentation standards
+
+4. **State Management Patterns**
+   - When to use TanStack Query vs local state
+   - State synchronization patterns
+   - Optimistic updates
+
+5. **Monitoring and Logging**
+   - Structured logging patterns
+   - Error tracking integration
+   - Performance monitoring
+   - User analytics patterns
+
+6. **Internationalization (i18n)**
+   - Translation key naming
+   - Locale handling
+   - Date/time formatting by locale
+
+### Enhancement Opportunities
+
+1. **Decision Trees**: Add more decision trees to cursor rules for common scenarios
+2. **Code Examples**: Expand code examples in both standards and rules
+3. **Migration Guides**: Add migration guides for breaking changes
+4. **Quick Reference**: Create a quick reference card for common patterns
+5. **Visual Diagrams**: Add architecture diagrams to standards where helpful
+
+## Verification Checklist
+
+- [x] All standards have corresponding cursor rules
+- [x] All cursor rules have corresponding standards
+- [x] All cross-references are correct and working
+- [x] No contradictions between standards and rules
+- [x] Cursor rules are optimized for AI agents
+- [x] Standards are human-readable and comprehensive
+- [x] Naming is consistent (00-12)
+- [x] Traceability is clear and bidirectional
+
+## Conclusion
+
+The standards and cursor rules are now fully aligned with:
+
+✅ **Complete traceability** - Every standard has a corresponding rule and vice versa  
+✅ **No contradictions** - Standards and rules are consistent  
+✅ **No gaps** - All content is present in both formats  
+✅ **AI optimization** - Rules are optimized for Cursor with decision trees and clear directives  
+✅ **Human readability** - Standards provide comprehensive documentation  
+
+The alignment ensures that:
+- Developers can read comprehensive standards documentation
+- AI agents can follow optimized rules for code generation
+- Both sources of truth are kept in sync
+- Traceability is clear and bidirectional
+
+## Maintenance
+
+To keep standards and rules aligned:
+
+1. **When updating a standard**: Update the corresponding rule
+2. **When updating a rule**: Update the corresponding standard
+3. **When adding a new standard**: Create a corresponding rule with the same number
+4. **When adding a new rule**: Create a corresponding standard with the same number
+5. **Regular reviews**: Review alignment quarterly or after major changes
+
+---
+
+**Last Updated**: 2025-01-28  
+**Next Review**: 2025-04-28
+

package/docs/standards/README.md

@@ -3,21 +3,50 @@
 ## Purpose
 This document is the single source of truth for all engineering standards for pace-core and consuming apps.
 
-## pace-core Standards
-- 01-architecture-standard.md
-- 02-api-and-rpc-standard.md
-- 03-component-standard.md
-- 04-code-style-standard.md
-- 05-security-standard.md
-- 06-testing-and-docs-standard.md
+## pace-core Standards (aligned with Cursor rule filenames)
+
+Each standard document has a corresponding Cursor rule file (`.mdc`) that enforces the standard automatically. The numbering ensures traceability. Standards 00-09 are core standards, while 10-12 are enhanced standards covering additional best practices.
+
+| Standard | Cursor Rule | Purpose |
+|----------|------------|---------|
+| **00-pace-core-compliance.md** | `00-pace-core-compliance.mdc` | Enforce pace-core usage patterns and prevent custom solutions |
+| **01-standards-compliance.md** | `01-standards-compliance.mdc` | Enforce all pace-core standards across architecture, API, components, code style, security, testing, and RBAC/RLS |
+| **02-project-structure.md** | `02-project-structure.mdc` | Define standard folder structure and file organization |
+| **03-solid-principles.md** | `03-solid-principles.mdc` | Enforce SOLID architecture principles |
+| **04-testing-standards.md** | `04-testing-standards.mdc` | Enforce testing framework consistency and standards |
+| **05-bug-reports-and-features.md** | `05-bug-reports-and-features.mdc` | Standardized templates for bug reports and feature requests |
+| **06-code-quality.md** | `06-code-quality.mdc` | Enforce code quality standards including TypeScript, ESLint, formatting, performance, and accessibility |
+| **07-tech-stack-compliance.md** | `07-tech-stack-compliance.mdc` | Enforce tech stack compliance including Tailwind v4, React 19+, Supabase, and other required technologies |
+| **08-markup-quality.md** | `08-markup-quality.mdc` | Enforce clean markup standards, semantic HTML usage, and pace-core component patterns |
+| **09-rbac-compliance.md** | `09-rbac-compliance.mdc` | Enforce RBAC contract compliance - strict rules for permission checking, page protection, and RBAC usage patterns |
+| **10-error-handling-patterns.md** | `10-error-handling-patterns.mdc` | Enforce consistent error handling patterns including type-safe errors, user-friendly messages, and proper logging |
+| **11-performance-optimization.md** | `11-performance-optimization.mdc` | Enforce performance optimization patterns including React memoization, database query optimization, and caching strategies |
+| **12-ci-cd-integration.md** | `12-ci-cd-integration.mdc` | Enforce CI/CD integration patterns including automated quality checks, deployment processes, and security scanning |
+
+**Note**: Standards are human-readable documentation. Rules are AI-optimized directives for Cursor. Both should be kept in sync. Standards 00-09 are core standards, while 10-12 are enhanced standards covering additional best practices.
 
 ## Consuming App Standards
-- 01-app-architecture.md
-- 02-pace-core-integration.md
-- 03-domain-model.md
-- 04-app-security-and-rbac.md
-- 05-testing-strategy.md
-- 06-ai-collaboration.md
+
+All standards in this directory apply to consuming apps. The standards are organized by topic:
+
+### Core Standards (00-09)
+These are fundamental standards that all consuming apps must follow:
+- **00-pace-core-compliance.md** - Use pace-core components, hooks, and utilities
+- **01-standards-compliance.md** - Meta-standard for precedence and traceability
+- **02-project-structure.md** - Standard folder structure and file organization
+- **03-solid-principles.md** - SOLID architecture principles
+- **04-testing-standards.md** - Testing framework consistency
+- **05-bug-reports-and-features.md** - Issue reporting templates
+- **06-code-quality.md** - TypeScript, ESLint, formatting, accessibility
+- **07-tech-stack-compliance.md** - Required technology versions
+- **08-markup-quality.md** - Clean markup, semantic HTML, CSS configuration
+- **09-rbac-compliance.md** - RBAC contract and RLS policy patterns
+
+### Enhanced Standards (10-12)
+These are best practice standards for advanced patterns:
+- **10-error-handling-patterns.md** - Consistent error handling
+- **11-performance-optimization.md** - Performance best practices
+- **12-ci-cd-integration.md** - CI/CD pipeline patterns
 
 ## Precedence
 1. Security
@@ -48,26 +77,26 @@ node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs
 
 ### Rule Files
 
-The cursor rules cover:
-- **00-pace-core-compliance** - Enforce pace-core usage patterns
-- **01-standards-compliance** - Enforce all standards (this document)
-- **02-project-structure** - Define standard folder structure
-- **03-solid-principles** - Enforce SOLID architecture
-- **04-testing-standards** - Enforce testing consistency
-- **05-bug-reports-and-features** - Templates for issue reporting
-- **06-code-quality** - Enforce code quality standards
-- **07-tech-stack-compliance** - Enforce tech stack versions
-- **08-markup-quality** - Enforce clean markup standards, semantic HTML usage, and pace-core component patterns
-
-### Audit Tool
-
-Run comprehensive audits to check compliance:
-
-```bash
-node node_modules/@jmruthers/pace-core/scripts/audit-consuming-app.cjs
-```
-
-This generates timestamped markdown reports in `audit/` directory.
+The cursor rules automatically enforce the corresponding standards. Each rule file (`.mdc`) is optimized for AI agents with:
+- Clear MUST/SHOULD/MAY directives
+- Decision trees for common scenarios
+- ✅/❌ code examples
+- Actionable checklists
+
+**Rule → Standard Mapping:**
+- **00-pace-core-compliance.mdc** → `00-pace-core-compliance.md`
+- **01-standards-compliance.mdc** → `01-standards-compliance.md`
+- **02-project-structure.mdc** → `02-project-structure.md`
+- **03-solid-principles.mdc** → `03-solid-principles.md`
+- **04-testing-standards.mdc** → `04-testing-standards.md`
+- **05-bug-reports-and-features.mdc** → `05-bug-reports-and-features.md`
+- **06-code-quality.mdc** → `06-code-quality.md`
+- **07-tech-stack-compliance.mdc** → `07-tech-stack-compliance.md`
+- **08-markup-quality.mdc** → `08-markup-quality.md`
+- **09-rbac-compliance.mdc** → `09-rbac-compliance.md`
+- **10-error-handling-patterns.mdc** → `10-error-handling-patterns.md`
+- **11-performance-optimization.mdc** → `11-performance-optimization.md`
+- **12-ci-cd-integration.mdc** → `12-ci-cd-integration.md`
 
 ### Documentation
 

package/docs/troubleshooting/organisation-context-setup.md

@@ -1,37 +1,51 @@
 ---
-lastUpdated: 2025-11-18T15:00:00+11:00
-version: 0.5.181
+lastUpdated: 2026-01-06T15:00:00+11:00
+version: 0.6.x
 reviewedBy: documentation-standards-audit
 ---
 
 # Organisation Context Setup Troubleshooting
 
-This guide helps you resolve the `unrecognized configuration parameter "app.organisation_id"` error that occurs when using PACE Core with Supabase.
+> **⚠️ IMPORTANT UPDATE (v0.6.x)**: The `set_organisation_context` and `get_organisation_context` functions have been **removed** in pace-core v0.6.x. Organisation context is now handled automatically via secure Supabase client headers.
 
-## 🚨 The Error
+## ✅ Current Implementation (v0.6.x+)
+
+Organisation context is now handled automatically:
+
+1. **Secure Supabase Client**: The `useSecureSupabase()` hook automatically injects organisation context headers
+2. **Explicit Parameters**: RPC functions receive `p_organisation_id` as explicit parameters
+3. **RLS Policies**: Row Level Security policies use `auth.uid()` and `organisation_id` columns directly
+
+**No manual context setting is required.** The secure client handles this automatically.
+
+## 🚨 Legacy Error (v0.5.x and earlier)
+
+If you're seeing this error, you may be using an older version of pace-core:
 
 ```
 Error loading units: unrecognized configuration parameter "app.organisation_id"
 ```
 
-**Console Error:**
-```
-Supabase error fetching units: Object { 
-  code: "42704", 
-  details: null, 
-  hint: null, 
-  message: 'unrecognized configuration parameter "app.organisation_id"' 
-}
-```
+**This error should not occur in v0.6.x+** as the functions have been removed.
 
-## 🔍 Root Cause
+## 🔍 If You Still See Errors
 
-This error occurs when:
-1. The Supabase database doesn't have the `set_organisation_context` function
-2. The `app.organisation_id` configuration parameter isn't available
-3. The organisation context isn't being set before making database queries
+If you're using pace-core v0.6.x+ and still seeing context-related errors:
 
-## ✅ Solution: Database Setup
+1. **Verify you're using `useSecureSupabase()`**: Always use the secure client from the hook, not the base client
+2. **Check RPC parameters**: Ensure RPC functions receive `p_organisation_id` as explicit parameters
+3. **Verify RLS policies**: RLS policies should use `auth.uid()` and `organisation_id` columns, not session variables
+
+## 📚 Legacy Documentation (v0.5.x)
+
+The following information is for reference only (v0.5.x and earlier):
+
+### Legacy Solution: Database Setup
+
+**Note**: These functions are no longer needed in v0.6.x+. This section is for historical reference only.
+
+<details>
+<summary>Click to view legacy setup (v0.5.x)</summary>
 
 ### Step 1: Create the Organisation Context Functions
 
@@ -282,6 +296,15 @@ If you're still experiencing problems:
 
 The key is making sure the database has the organisation context functions and your RLS policies use them correctly.
 
+</details>
+
+## ✅ Current Best Practices (v0.6.x+)
+
+1. **Always use `useSecureSupabase()`**: This hook automatically handles organisation context
+2. **Pass explicit parameters**: RPC functions should receive `p_organisation_id` as explicit parameters
+3. **Use RLS policies correctly**: Policies should use `auth.uid()` and `organisation_id` columns directly
+4. **No manual context setting**: The secure client handles everything automatically
+
 ## ♿ Accessibility
 
 Organisation context setup doesn't directly impact accessibility, but ensure:

package/eslint-config-pace-core.cjs

@@ -35,17 +35,17 @@ try {
 let paceCoreRules = {};
 try {
   // Try source path first (for development)
-  const sourceRulesPath = path.resolve(__dirname, 'src/eslint-rules/pace-core-compliance.cjs');
+  const sourceRulesPath = path.resolve(__dirname, 'src/eslint-rules/index.cjs');
   if (fs.existsSync(sourceRulesPath)) {
     paceCoreRules = require(sourceRulesPath).rules;
   } else {
     // Try dist path (for published package)
-    const distRulesPath = path.resolve(__dirname, 'dist/eslint-rules/pace-core-compliance.cjs');
+    const distRulesPath = path.resolve(__dirname, 'dist/eslint-rules/index.cjs');
     if (fs.existsSync(distRulesPath)) {
       paceCoreRules = require(distRulesPath).rules;
     } else {
       // Try relative to current working directory (for consuming apps)
-      const cwdRulesPath = path.resolve(process.cwd(), 'node_modules/@jmruthers/pace-core/dist/eslint-rules/pace-core-compliance.cjs');
+      const cwdRulesPath = path.resolve(process.cwd(), 'node_modules/@jmruthers/pace-core/dist/eslint-rules/index.cjs');
       if (fs.existsSync(cwdRulesPath)) {
         paceCoreRules = require(cwdRulesPath).rules;
       }
@@ -77,12 +77,28 @@ module.exports = [
       }
     },
     rules: {
-      // Use pace-core compliance rules
+      // Import rules
       'pace-core-compliance/no-restricted-imports': 'error',
+      
+      // Compliance rules
       'pace-core-compliance/prefer-pace-core-components': 'warn',
       'pace-core-compliance/prefer-pace-core-hooks': 'warn',
       'pace-core-compliance/prefer-pace-core-utils': 'warn',
       'pace-core-compliance/no-local-component-duplication': 'error',
+      'pace-core-compliance/no-inline-styles': 'error',
+      
+      // Component rules
+      'pace-core-compliance/prefer-pace-core-form': 'error',
+      
+      // RBAC rules
+      'pace-core-compliance/no-direct-supabase-client': 'error',
+      'pace-core-compliance/rbac-permission-loading': 'error',
+      'pace-core-compliance/no-direct-rbac-rpc': 'error',
+      'pace-core-compliance/no-direct-rbac-table': 'error',
+      'pace-core-compliance/no-hardcoded-role-checks': 'error',
+      'pace-core-compliance/rbac-use-resource-names-constants': 'error',
+      'pace-core-compliance/no-rbac-wrapper-components': 'error',
+      'pace-core-compliance/no-rbac-wrapper-functions': 'error',
       
       // Also use standard no-restricted-imports (ESLint 9 flat config format)
       // Note: ESLint 9 uses a simpler array format

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jmruthers/pace-core",
-  "version": "0.6.4",
-  "description": "Clean, modern React component library with Tailwind v4 styling and native utilities",
+  "version": "0.6.6",
+  "description": "React component library with Tailwind v4",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -42,6 +42,11 @@
       "import": "./dist/utils.js",
       "default": "./dist/utils.js"
     },
+    "./icons": {
+      "types": "./dist/icons/index.d.ts",
+      "import": "./dist/icons/index.js",
+      "default": "./dist/icons/index.js"
+    },
     "./rbac": {
       "types": "./dist/rbac/index.d.ts",
       "import": "./dist/rbac/index.js",
@@ -53,9 +58,9 @@
       "default": "./dist/rbac/eslint-rules.js"
     },
     "./eslint-rules": {
-      "require": "./dist/eslint-rules/pace-core-compliance.cjs",
-      "import": "./dist/eslint-rules/pace-core-compliance.cjs",
-      "default": "./dist/eslint-rules/pace-core-compliance.cjs"
+      "require": "./dist/eslint-rules/index.cjs",
+      "import": "./dist/eslint-rules/index.cjs",
+      "default": "./dist/eslint-rules/index.cjs"
     },
     "./eslint-config": "./eslint-config-pace-core.cjs",
     "./styles/core.css": "./src/styles/core.css",
@@ -69,12 +74,13 @@
       "default": "./vite-plugin-tailwind-v4.js"
     },
     "./docs": "./docs/README.md",
+    "./docs/dependencies": "./docs/getting-started/dependencies.md",
     "./package.json": "./package.json",
     "./core-usage-manifest.json": "./core-usage-manifest.json",
     "./cursor-rules": "./cursor-rules",
     "./scripts/install-cursor-rules": "./scripts/install-cursor-rules.cjs",
+    "./scripts/audit-dependencies": "./scripts/audit/audit-dependencies.cjs",
     "./scripts/audit": "./scripts/audit/index.cjs",
-    "./scripts/audit-consuming-app": "./scripts/audit-consuming-app.cjs",
     "./source": {
       "import": "./src/index.ts",
       "default": "./src/index.ts"
@@ -95,6 +101,10 @@
       "import": "./src/utils/index.ts",
       "default": "./src/utils/index.ts"
     },
+    "./source/icons": {
+      "import": "./src/icons/index.ts",
+      "default": "./src/icons/index.ts"
+    },
     "./source/types": {
       "import": "./src/types/index.ts",
       "default": "./src/types/index.ts"
@@ -148,6 +158,7 @@
   "scripts": {
     "_comment_build": "Build package and documentation",
     "build": "tsup && node scripts/build-css.js",
+    "build:fast": "SKIP_CLEAN=true NODE_ENV=development tsup && node scripts/build-css.js",
     "build:watch": "tsup --watch",
     "build:docs": "node scripts/build-docs-incremental.js",
     "build:docs:force": "node scripts/build-docs-incremental.js --force",
@@ -201,17 +212,11 @@
   "author": "PACE Team",
   "license": "MIT",
   "peerDependencies": {
-    "@radix-ui/react-checkbox": "^1.0.0",
-    "@radix-ui/react-dialog": "^1.0.0",
-    "@radix-ui/react-label": "^2.0.0",
-    "@radix-ui/react-slot": "^1.0.0",
-    "@radix-ui/react-switch": "^1.1.0",
-    "@radix-ui/react-tabs": "^1.0.0",
-    "@radix-ui/react-toast": "^1.0.0",
-    "@radix-ui/react-tooltip": "^1.0.0",
+    "@tanstack/react-query": "^5.90.0",
     "@tanstack/react-table": "^8.0.0",
     "clsx": "^2.0.0",
-    "lucide-react": "^0.400.0",
+    "date-fns": "^3.0.0",
+    "date-fns-tz": "^3.0.0",
     "react": "^19.0.0",
     "react-day-picker": "^9.0.0",
     "react-dom": "^19.0.0",
@@ -247,14 +252,19 @@
   },
   "dependencies": {
     "@hookform/resolvers": "^3.9.0",
-    "@supabase/supabase-js": "^2.49.10",
-    "@tanstack/react-query": "^5.56.2",
-    "@tanstack/react-virtual": "^3.13.12",
-    "date-fns": "^3.0.0",
-    "date-fns-tz": "^3.0.0",
+    "@radix-ui/react-checkbox": "^1.0.0",
+    "@radix-ui/react-label": "^2.0.0",
+    "@radix-ui/react-slot": "^1.0.0",
+    "@radix-ui/react-switch": "^1.1.0",
+    "@radix-ui/react-tabs": "^1.0.0",
+    "@radix-ui/react-toast": "^1.0.0",
+    "@radix-ui/react-tooltip": "^1.0.0",
+    "@supabase/supabase-js": "^2.89.0",
+    "@tanstack/react-virtual": "^3.13.16",
     "lodash.debounce": "^4.0.8",
     "lodash.throttle": "^4.1.1",
+    "lucide-react": "^0.400.0",
     "papaparse": "^5.5.3",
-    "react-is": "^19.2.0"
+    "react-is": "^19.2.3"
   }
 }