@jmruthers/pace-core 0.6.6 → 0.6.7

package/docs/standards/{00-pace-core-compliance.md → 1-pace-core-compliance-standards.md}

@@ -1,6 +1,6 @@
-# pace-core Compliance Enforcement
+# pace-core Compliance Standards
 
-**🤖 Cursor Rule**: See [00-pace-core-compliance.mdc](../../cursor-rules/00-pace-core-compliance.mdc) for AI-optimized directives that automatically enforce these standards.
+**🤖 Cursor Rule**: See [01-pace-core-compliance.mdc](../../cursor-rules/01-pace-core-compliance.mdc) for AI-optimized directives that automatically enforce these standards.
 
 This guide explains how to enforce pace-core usage patterns in consuming apps to ensure consistent design, reduce duplication, and maintain high code quality.
 
@@ -8,8 +8,8 @@ This guide explains how to enforce pace-core usage patterns in consuming apps to
 
 pace-core provides a comprehensive enforcement system that includes:
 
-1. **ESLint Rules** - Real-time linting during development (15 rules)
-2. **Static Analysis Script** - Comprehensive codebase scanning for file-system and config checks
+1. **ESLint Rules** - Real-time linting during development (organized by standards: 01, 04, 05, 06, 07, 08)
+2. **Audit Tool** - Comprehensive system-level analysis organized by standards (01-09)
 3. **ESLint Config Preset** - Easy setup for consuming apps
 4. **Cursor Rules Integration** - AI-assisted enforcement via Cursor IDE
 
@@ -63,16 +63,17 @@ npm install @jmruthers/pace-core
 
 ### Step 2: Setup ESLint (Recommended)
 
-**Option A: Automated Setup (Easiest)**
+**Automated Setup (Easiest)**
 
-Use the installation script to set up both Cursor rules and ESLint:
+Use the installation script to set up ESLint:
 
 ```bash
-node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs
+npm run setup:eslint
+# or
+node node_modules/@jmruthers/pace-core/scripts/install-eslint-config.cjs
 ```
 
 This script will:
-- ✅ Install Cursor rules to `.cursor/rules/`
 - ✅ Configure ESLint to use pace-core rules
 - ✅ Create `eslint.config.js` if it doesn't exist
 - ✅ Add pace-core config to existing ESLint config
@@ -80,8 +81,6 @@ This script will:
 
 **Options:**
 - `--force` - Force update even if already configured
-- `--skip-cursor` - Skip Cursor rules installation
-- `--skip-eslint` - Skip ESLint config setup
 
 **Option B: Manual Setup**
 
@@ -134,7 +133,27 @@ export default [
 
 ### Step 3: Setup Cursor Rules (Optional but Recommended)
 
-To enable AI-assisted enforcement in Cursor IDE, copy the pace-core cursor rules to your project:
+**Automated Setup (Easiest)**
+
+Use the installation script to set up Cursor rules:
+
+```bash
+npm run setup:cursor-rules
+# or
+node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs
+```
+
+This script will:
+- ✅ Install Cursor rules to `.cursor/rules/`
+- ✅ Create backups before updating existing rules
+- ✅ Automatically update pace-core rules when they change
+
+**Options:**
+- `--force` - Force update even if already configured
+
+**Manual Setup (Alternative)**
+
+To manually enable AI-assisted enforcement in Cursor IDE, copy the pace-core cursor rules to your project:
 
 ```bash
 # Create .cursor/rules directory if it doesn't exist
@@ -144,7 +163,7 @@ mkdir -p .cursor/rules
 cp node_modules/@jmruthers/pace-core/cursor-rules/*.mdc .cursor/rules/
 ```
 
-Or manually create `.cursor/rules/00-pace-core-compliance.mdc` and reference the pace-core rules:
+Or manually create `.cursor/rules/01-pace-core-compliance.mdc` and reference the pace-core rules:
 
 ```markdown
 ---
@@ -155,7 +174,7 @@ alwaysApply: false
 
 # pace-core Compliance
 
-**📚 Full Documentation**: See [pace-core compliance docs](node_modules/@jmruthers/pace-core/docs/standards/00-pace-core-compliance.md)
+**📚 Full Documentation**: See [pace-core compliance docs](node_modules/@jmruthers/pace-core/docs/standards/1-pace-core-compliance-standards.md)
 
 **🔧 ESLint Setup**: Ensure ESLint is configured with `@jmruthers/pace-core/eslint-config`
 
@@ -179,63 +198,32 @@ See the full documentation for complete rules and examples.
 - Works alongside ESLint for comprehensive enforcement
 - Provides explanations and examples in real-time
 
-### Option 2: Manual ESLint Rules Setup
+## ESLint Rules
 
-If you prefer more control, you can import the rules directly. Note: The rules are CommonJS, so use `createRequire` in ES modules:
+pace-core provides ESLint rules organized by standards (01, 04, 05, 06, 07, 08). Rules are organized to match the 10-file standards structure:
 
-**For ES Module ESLint Config:**
-```javascript
-// eslint.config.js
-import { createRequire } from 'module';
-const require = createRequire(import.meta.url);
-const paceCoreRules = require('@jmruthers/pace-core/eslint-rules').rules;
-
-export default [
-  {
-    plugins: {
-      'pace-core-compliance': {
-        rules: paceCoreRules
-      }
-    },
-    rules: {
-      'pace-core-compliance/no-restricted-imports': 'error',
-      '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'
-    }
-  }
-];
-```
+- **Standard 1 (pace-core Compliance)**: 6 rules
+- **Standard 4 (Code Quality)**: 3 rules
+- **Standard 5 (Styling)**: 1 rule
+- **Standard 6 (Security & RBAC)**: 8 rules
+- **Standard 7 (API & Tech Stack)**: 3 rules
+- **Standard 8 (Testing)**: 1 rule
 
-**For CommonJS ESLint Config:**
-```javascript
-// eslint.config.cjs
-const paceCoreRules = require('@jmruthers/pace-core/eslint-rules').rules;
+**Total: 22 rules** organized across 6 standards files.
 
-module.exports = [
-  {
-    plugins: {
-      'pace-core-compliance': {
-        rules: paceCoreRules
-      }
-    },
-    rules: {
-      'pace-core-compliance/no-restricted-imports': 'error',
-      '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'
-    }
-  }
-];
-```
+### Rule Organization
 
-## ESLint Rules
+Rules are organized in `packages/core/eslint-rules/rules/`:
+- `01-pace-core-compliance.cjs` - pace-core usage patterns
+- `04-code-quality.cjs` - Naming conventions, component/type naming
+- `05-styling.cjs` - Inline styles
+- `06-security-rbac.cjs` - Security and RBAC patterns
+- `07-api-tech-stack.cjs` - RPC naming, React 19+, import.meta.env
+- `08-testing.cjs` - Test file naming
 
-pace-core provides **15 ESLint rules** organized into four categories:
+### Detailed Rule Descriptions
 
-### Import Rules
+#### Import Rules
 
 #### no-restricted-imports
 
@@ -603,25 +591,6 @@ The script generates a color-coded terminal report showing:
 - 💡 **Suggestions** - Recommendations for improvement
 - ✅ **Summary** - Overall compliance status
 
-Example output:
-```
-═══════════════════════════════════════════════════════════
-  pace-core Compliance Report
-═══════════════════════════════════════════════════════════
-
-❌ Restricted Imports Found: 3
-
-  • src/components/CustomDialog.tsx:5
-    Import: @radix-ui/react-dialog
-    Reason: Use Dialog component from pace-core instead
-
-Summary:
-  Total Issues: 3
-  - Restricted Imports: 3
-  - Duplicate Components/Hooks/Utils: 0
-  - Suggestions: 0
-```
-
 ## Best Practices
 
 ### 1. Always Import from pace-core
@@ -683,116 +652,93 @@ Before creating a new component, check if pace-core already provides it:
 2. Check `core-usage-manifest.json` for available components
 3. Search pace-core exports
 
-## Troubleshooting
-
-### ESLint Rules Not Working
-
-1. **Verify plugin is loaded**: Check that the config is imported correctly:
-   ```javascript
-   // In your eslint.config.js, add temporarily:
-   import paceCoreConfig from '@jmruthers/pace-core/eslint-config';
-   console.log('Config:', paceCoreConfig);
-   console.log('Has plugins:', paceCoreConfig[0]?.plugins);
-   ```
-
-2. **Check rule names**: Rules must be prefixed with `pace-core-compliance/`
-
-3. **Verify manifest exists**: Rules load from `core-usage-manifest.json` in the pace-core package
-
-4. **CommonJS/ES Module issues**: If you're using ES modules and rules aren't loading:
-   - Ensure you're using the config preset (Option 1) which handles this automatically
-   - Or use `createRequire` when importing rules directly (Option 2)
-
-5. **Verify rules are available**: Check that the rules file exists:
-   ```bash
-   ls node_modules/@jmruthers/pace-core/dist/eslint-rules/index.cjs
-   ```
-
-6. **Check rule count**: Verify all 15 rules are loaded:
-   ```bash
-   node -e "const rules = require('@jmruthers/pace-core/eslint-rules'); console.log('Rules:', Object.keys(rules.rules).length);"
-   ```
-   Should output: `Rules: 15`
-
-### Static Analysis Script Errors
-
-1. **Manifest not found**: Ensure `core-usage-manifest.json` exists in pace-core package
-2. **No files scanned**: Check that you're running from the project root
-3. **Permission errors**: Ensure script has read access to source files
-
-### False Positives
-
-If you encounter false positives:
-
-1. **Component name conflicts**: If you have a legitimate reason to create a local component with a pace-core name, consider:
-   - Renaming your component
-   - Using a namespace/prefix
-   - Documenting why pace-core doesn't meet your needs
+## MUST: Provider Nesting Order
 
-2. **Hook/Util patterns**: The pattern matching may flag similar names. Review the suggestion and decide if migration makes sense.
+**⚠️ CRITICAL: Provider nesting order matters!** Incorrect nesting causes React context errors.
 
-## Integration with CI/CD
+**MUST** nest providers in this exact order (outermost to innermost):
 
-While CI/CD integration is not included in the initial release, you can easily add it:
+1. `QueryClientProvider` (outermost)
+2. `BrowserRouter`
+3. `UnifiedAuthProvider`
+4. `OrganisationProvider`
+5. `App` (innermost)
 
-```yaml
-# .github/workflows/pace-core-compliance.yml
-name: pace-core Compliance
+```tsx
+// ✅ CORRECT: main.tsx
+import { BrowserRouter } from 'react-router-dom';
+import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+import { UnifiedAuthProvider, OrganisationProvider } from '@jmruthers/pace-core';
+import { createClient } from '@supabase/supabase-js';
 
-on: [push, pull_request]
+const queryClient = new QueryClient();
+const supabase = createClient(
+  import.meta.env.VITE_SUPABASE_URL,
+  import.meta.env.VITE_SUPABASE_PUBLISHABLE_KEY
+);
 
-jobs:
-  compliance:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-      - run: npm ci
-      - run: npm run check:pace-core
-      - run: npm run lint
+createRoot(document.getElementById("root")!).render(
+  <QueryClientProvider client={queryClient}>
+    <BrowserRouter>
+      <UnifiedAuthProvider supabaseClient={supabase} appName="YourApp">
+        <OrganisationProvider>
+          <App />
+        </OrganisationProvider>
+      </UnifiedAuthProvider>
+    </BrowserRouter>
+  </QueryClientProvider>
+);
 ```
 
-## Verification
-
-After setting up the ESLint config, verify it's working:
-
-1. **Check ESLint can load the config**:
-   ```bash
-   npx eslint --print-config src/App.tsx
-   ```
-   Look for `pace-core-compliance` in the plugins section.
-
-2. **Test with a violation**: Create a test file that imports a restricted library:
-   ```typescript
-   // test-violation.ts
-   import { Dialog } from '@radix-ui/react-dialog'; // Should trigger error
-   ```
-   Run ESLint and verify it reports the violation.
+**Common mistakes to avoid:**
+- ❌ `BrowserRouter` inside `UnifiedAuthProvider` (causes Router context errors)
+- ❌ `UnifiedAuthProvider` wrapping `BrowserRouter` (causes context errors)
+- ❌ Missing `BrowserRouter` (causes `useNavigate` errors)
 
-3. **Run static analysis**: Use the compliance script to get a full report:
-   ```bash
-   npm run check:pace-core
-   ```
+## MUST: Vite Configuration
 
-## Getting Help
+**⚠️ CRITICAL: Vite configuration prevents React context mismatches!**
 
-- **Documentation**: See [pace-core docs](../README.md)
-- **Issues**: Report false positives or rule issues
-- **Manifest**: Check `core-usage-manifest.json` for available exports
-- **ESLint Config**: The config file is at `@jmruthers/pace-core/eslint-config` (CommonJS)
-- **ESLint Rules**: The rules are at `@jmruthers/pace-core/eslint-rules` (CommonJS)
+**MUST** configure Vite to exclude `@jmruthers/pace-core` and `react-router-dom` from pre-bundling:
 
-## File Locations
+```typescript
+// vite.config.ts
+import { defineConfig } from 'vite';
+import react from '@vitejs/plugin-react';
+import path from 'path';
+
+export default defineConfig({
+  plugins: [react()],
+  resolve: {
+    alias: {
+      '@': path.resolve(__dirname, './src'),
+    },
+    // CRITICAL: Dedupe React dependencies
+    dedupe: ['react', 'react-dom', 'react-router-dom'],
+  },
+  optimizeDeps: {
+    include: [
+      'react',
+      'react-dom',
+      'react/jsx-runtime',
+    ],
+    // CRITICAL: Exclude pace-core to prevent React context mismatches
+    exclude: ['@jmruthers/pace-core', 'react-router-dom'],
+  },
+});
+```
 
-When installed in a consuming app, the compliance tools are available at:
+**Why this matters:**
+- Pre-bundling `@jmruthers/pace-core` creates separate React instances
+- This causes "useUnifiedAuth must be used within a UnifiedAuthProvider" errors
+- Excluding it ensures pace-core uses the same React instance as your app
+- `react-router-dom` must also be excluded and deduped to prevent Router context errors
 
-- **ESLint Config**: `node_modules/@jmruthers/pace-core/eslint-config-pace-core.cjs`
-- **ESLint Rules**: `node_modules/@jmruthers/pace-core/dist/eslint-rules/index.cjs`
-- **Rule Modules**: `node_modules/@jmruthers/pace-core/dist/eslint-rules/rules/*.cjs`
-- **Rule Utils**: `node_modules/@jmruthers/pace-core/dist/eslint-rules/utils/*.cjs`
-- **Static Analysis Script**: `node_modules/@jmruthers/pace-core/scripts/check-pace-core-compliance.cjs`
-- **Manifest**: `node_modules/@jmruthers/pace-core/core-usage-manifest.json`
-- **Cursor Rules**: `node_modules/@jmruthers/pace-core/cursor-rules/*.mdc`
+**If you encounter context errors:**
+1. Verify `@jmruthers/pace-core` is in `optimizeDeps.exclude`
+2. Verify `react-router-dom` is in both `resolve.dedupe` and `optimizeDeps.exclude`
+3. Clear Vite cache: `rm -rf node_modules/.vite`
+4. Restart dev server
 
 ## MUST: Use Secure Supabase Client
 
@@ -906,7 +852,23 @@ function useSecureSupabase(
 
 **NO OTHER EXCEPTIONS ARE PERMITTED** - All other uses of `createClient()` are security violations and MUST be fixed.
 
-### Detection / Audit
+### Detection / Audit Tool
+
+The audit tool (`npm run audit:pace-core`) performs comprehensive system-level analysis organized by standards:
+
+- **Standard 1 (pace-core Compliance)**: Provider nesting, core styles import, RBAC setup, Vite aliases, secure Supabase client location, Cursor rules, ESLint config
+- **Standard 2 (Project Structure)**: Directory structure, config files, import paths, test colocation, Supabase structure
+- **Standard 3 (Architecture)**: Component boundaries, ApiResult usage
+- **Standard 4 (Code Quality)**: TypeScript config, test coverage config
+- **Standard 5 (Styling)**: app.css structure, Tailwind v4 config
+- **Standard 6 (Security & RBAC)**: RLS policies, PagePermissionGuard coverage, Edge Functions RBAC
+- **Standard 7 (API & Tech Stack)**: RPC naming in SQL, tech stack versions, Vite config
+- **Standard 8 (Testing & Documentation)**: Test timeout config, testing tools, test structure
+- **Standard 9 (Operations)**: Error handling patterns, CI/CD config, error boundaries
+
+**Reference**: See [packages/core/audit-tool/](../../audit-tool/) for audit tool implementation.
+
+### Detection / Audit (Legacy)
 
 - `rg "createClient\(" src` must return **exactly ONE match** in the file that creates the base client for `UnifiedAuthProvider`.
 - That file MUST be one of: `main.tsx`, `App.tsx`, or `lib/supabase.ts` (or `.jsx`/`.js` equivalents).
@@ -938,8 +900,10 @@ If you encounter a situation where a rule seems to conflict with a legitimate re
 **Example of proper documentation:**
 ```tsx
 // @pace-core-compliance-exception: Legacy integration requires direct Supabase client
-// TODO: Migrate to useSecureSupabase() when legacy system is updated
-// See: https://github.com/your-org/pace-core/issues/123
+// Reason: Third-party service requires unauthenticated client for initial handshake
+// Migration plan: Migrate to useSecureSupabase() when legacy system is updated (Q2 2025)
+// Tracking issue: https://github.com/your-org/pace-core/issues/123
+// Expected removal date: Q2 2025
 const legacyClient = createClient(...);
 ```
 
@@ -958,10 +922,65 @@ During audits, documented exceptions will be:
 
 **Invalid exceptions** (undocumented, unnecessary, or security-related) will be flagged as violations requiring remediation.
 
+## Troubleshooting
+
+### ESLint Rules Not Working
+
+1. **Verify plugin is loaded**: Check that the config is imported correctly
+2. **Check rule names**: Rules must be prefixed with `pace-core-compliance/`
+3. **Verify manifest exists**: Rules load from `core-usage-manifest.json` in the pace-core package
+4. **CommonJS/ES Module issues**: If you're using ES modules and rules aren't loading, ensure you're using the config preset which handles this automatically
+5. **Verify rules are available**: Check that the rules file exists
+6. **Check rule count**: Verify all 15 rules are loaded
+
+### Static Analysis Script Errors
+
+1. **Manifest not found**: Ensure `core-usage-manifest.json` exists in pace-core package
+2. **No files scanned**: Check that you're running from the project root
+3. **Permission errors**: Ensure script has read access to source files
+
+### False Positives
+
+If you encounter false positives:
+
+1. **Component name conflicts**: If you have a legitimate reason to create a local component with a pace-core name, consider:
+   - Renaming your component
+   - Using a namespace/prefix
+   - Documenting why pace-core doesn't meet your needs
+
+2. **Hook/Util patterns**: The pattern matching may flag similar names. Review the suggestion and decide if migration makes sense.
+
+## Verification
+
+After setting up the ESLint config, verify it's working:
+
+1. **Check ESLint can load the config**:
+   ```bash
+   npx eslint --print-config src/App.tsx
+   ```
+   Look for `pace-core-compliance` in the plugins section.
+
+2. **Test with a violation**: Create a test file that imports a restricted library:
+   ```typescript
+   // test-violation.ts
+   import { Dialog } from '@radix-ui/react-dialog'; // Should trigger error
+   ```
+   Run ESLint and verify it reports the violation.
+
+3. **Run static analysis**: Use the compliance script to get a full report:
+   ```bash
+   npm run check:pace-core
+   ```
+
 ## Related Documentation
 
-- [Component Standards](./03-component-standard.md)
-- [API & RPC Standards](./02-api-and-rpc-standard.md)
-- [Getting Started Guide](../getting-started/README.md)
-- [RBAC Getting Started](../rbac/getting-started.md) - Secure client usage
+- [Standards Overview](./0-standards-overview.md) - Standards system overview
+- [Project Structure](./2-project-structure-standards.md) - Project structure and organization
+- [Security & RBAC](./6-security-rbac-standards.md) - RBAC and security standards
+- [API & Tech Stack](./7-api-tech-stack-standards.md) - API and tech stack standards
+
+---
 
+**Last Updated:** 2025-01-28  
+**Version:** 2.0.0  
+**Applies to:** All consuming apps using `@jmruthers/pace-core`

package/docs/standards/{02-project-structure.md → 2-project-structure-standards.md}

@@ -1,4 +1,4 @@
-# Project Structure Guide for Consuming Apps
+# Project Structure Standards
 
 **🤖 Cursor Rule**: See [02-project-structure.mdc](../../cursor-rules/02-project-structure.mdc) for AI-optimized directives that automatically enforce this structure.
 
@@ -37,8 +37,8 @@ Every consuming app **MUST** follow this base structure:
 your-app/
 ├── .cursor/
 │   └── rules/                    # Cursor rules (pace-core + local)
-│       ├── 00-pace-core-compliance.mdc
-│       ├── 01-standards-compliance.mdc
+│       ├── 00-standards-overview.mdc
+│       ├── 01-pace-core-compliance.mdc
 │       ├── 02-project-structure.mdc
 │       └── [local-rules].mdc
 │
@@ -79,7 +79,7 @@ your-app/
 │   │
 │   ├── App.tsx                   # Main app component
 │   ├── main.tsx                  # Application entry point
-│   └── app.css                   # Global styles (MUST follow 08-markup-quality.md)
+│   └── app.css                   # Global styles (MUST follow 5-styling-standards.md)
 │
 ├── supabase/                     # Supabase configuration
 │   ├── migrations/              # Database migrations
@@ -762,12 +762,6 @@ your-app/
    find src -type f -name "*.tsx" -exec sed -i '' 's|from.*EventCard|from "@/components/events/EventCard"|g' {} +
    ```
 
-   Or use a script:
-   ```typescript
-   // scripts/update-imports.ts
-   // Update imports programmatically
-   ```
-
 #### Phase 4: Cleanup
 
 1. **Remove Duplicate pace-core Components**
@@ -796,7 +790,6 @@ your-app/
    ```bash
    # Check pace-core compliance
    node node_modules/@jmruthers/pace-core/scripts/check-pace-core-compliance.cjs
-   
    ```
 
 3. **Verify Build**
@@ -849,26 +842,6 @@ your-app/
 - Ensure path aliases work in test environment
 - Update test setup files
 
-### Migration Tools
-
-**Automated Import Updates:**
-```bash
-# Using jscodeshift (if available)
-npx jscodeshift -t transform-imports src/
-```
-
-**Manual Find-and-Replace:**
-```bash
-# Update specific import patterns
-find src -type f -name "*.tsx" -exec sed -i '' 's|old/path|new/path|g' {} +
-```
-
-**TypeScript Compiler:**
-```bash
-# Check for import errors
-npx tsc --noEmit
-```
-
 ---
 
 ## Structure Checklist
@@ -960,26 +933,17 @@ import { Button } from '@jmruthers/pace-core';
 
 ---
 
-## Getting Help
-
-- **Documentation**: See [pace-core documentation](../../README.md)
-- **Standards**: Review other standards in this directory
-- **Cursor Rules**: Check `.cursor/rules/` for automated enforcement
-
----
-
 ## Related Documentation
 
-- [pace-core Compliance](./00-pace-core-compliance.md) - pace-core usage patterns
-- [Markup Quality](./08-markup-quality.md) - **CRITICAL: Required CSS configuration**
-- [Code Quality](./06-code-quality.md) - Code style and TypeScript standards
-- [Tech Stack](./07-tech-stack-compliance.md) - Tech stack requirements
-- [SOLID Principles](./03-solid-principles.md) - Architecture principles
-- [Cursor Rules Documentation](../../getting-started/cursor-rules.md)
+- [Standards Overview](./0-standards-overview.md) - Standards system overview
+- [pace-core Compliance](./1-pace-core-compliance-standards.md) - pace-core usage patterns
+- [Styling Standards](./5-styling-standards.md) - **CRITICAL: Required CSS configuration**
+- [Code Quality](./4-code-quality-standards.md) - Code style and TypeScript standards
+- [API & Tech Stack](./7-api-tech-stack-standards.md) - Tech stack requirements
+- [Architecture](./3-architecture-standards.md) - Architecture principles
 
 ---
 
 **Last Updated:** 2025-01-28  
-**Version:** 1.0.0  
+**Version:** 2.0.0  
 **Applies to:** All consuming apps using `@jmruthers/pace-core`
-