@jmruthers/pace-core 0.5.181 → 0.5.183

package/docs/best-practices/performance.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T17:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Performance Best Practices
@@ -1267,4 +1267,51 @@ describe('Performance Tests', () => {
 - [Best Practices Overview](./README.md) - General best practices
 - [Troubleshooting Performance Issues](../troubleshooting/README.md#performance-issues) - Performance debugging
 
+## ♿ Accessibility
+
+Performance optimizations should maintain accessibility:
+
+- **Lazy loading doesn't break screen readers** - Ensure lazy-loaded content is accessible
+- **Code splitting maintains keyboard navigation** - Verify keyboard navigation works after code splitting
+- **Memoization doesn't affect focus management** - Ensure focus handling remains correct
+- **Performance optimizations are tested with assistive technologies** - Verify optimizations don't break accessibility
+- **Loading states are announced** - Screen readers should announce performance-related loading states
+
+### Accessibility Best Practices
+
+1. **Test optimizations with screen readers** - Verify performance improvements don't break accessibility
+2. **Ensure keyboard navigation** - All optimized components should remain keyboard accessible
+3. **Maintain focus visibility** - Focus indicators should remain visible after optimizations
+4. **Test with assistive technologies** - Verify performance optimizations work with screen readers
+5. **Balance performance and accessibility** - Don't sacrifice accessibility for performance gains
+
+## ⚠️ Edge Cases
+
+### Performance vs Accessibility Trade-offs
+
+When performance optimizations impact accessibility:
+- Find balance between performance and accessibility
+- Test optimizations with assistive technologies
+- Ensure lazy loading doesn't break screen reader navigation
+- Verify code splitting maintains keyboard navigation
+- Document trade-offs when necessary
+
+### Over-Optimization Issues
+
+When over-optimization causes problems:
+- Monitor for premature optimization
+- Test optimizations in real-world scenarios
+- Profile before and after optimizations
+- Verify optimizations provide measurable benefits
+- Consider maintainability when optimizing
+
+### Performance Regression
+
+When performance degrades after optimizations:
+- Profile to identify bottlenecks
+- Test with realistic data volumes
+- Monitor performance metrics
+- Rollback optimizations if needed
+- Document performance regression causes
+
 For more information about optimizing your application, see the [Security Guide](./security.md) and [Testing Guide](./testing.md). 

package/docs/best-practices/security.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T17:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Security Best Practices
@@ -24,53 +24,59 @@ The security model in `@jmruthers/pace-core` is built on several layers:
 ### 1. Secure Password Requirements
 
 ```typescript
-import { validatePassword } from '@jmruthers/pace-core';
-
-const passwordRequirements = {
-  minLength: 8,
-  requireUppercase: true,
-  requireLowercase: true,
-  requireNumbers: true,
-  requireSpecialChars: true,
-};
+import { passwordSchema, securePasswordSchema, calculatePasswordStrength } from '@jmruthers/pace-core/utils/validation';
+import { isStrongPassword } from '@jmruthers/pace-core/utils/validation';
+
+// Using Zod schema (recommended)
+function validateUserPassword(password: string) {
+  const result = securePasswordSchema.safeParse(password);
+  if (!result.success) {
+    return { valid: false, errors: result.error.errors };
+  }
+  return { valid: true };
+}
 
-function validateUserPassword(password: string): boolean {
-  return validatePassword(password, passwordRequirements);
+// Using simple validation function
+function checkPasswordStrength(password: string) {
+  const strength = calculatePasswordStrength(password);
+  return {
+    isValid: strength.level !== 'very-weak' && strength.level !== 'weak',
+    strength: strength.level,
+    score: strength.score,
+    feedback: strength.feedback
+  };
 }
+
+// Basic validation
+const isValid = isStrongPassword(password); // Returns boolean
 ```
 
-### 2. Multi-Factor Authentication
+### 2. Password Strength Indicator
 
 ```typescript
-import { useUnifiedAuth } from '@jmruthers/pace-core';
+import { calculatePasswordStrength } from '@jmruthers/pace-core/utils/validation';
 
-function MFASetup() {
-  const { setupMFA, verifyMFA } = useUnifiedAuth();
-
-  const handleSetupMFA = async () => {
-    try {
-      const { qrCode, secret } = await setupMFA();
-      // Display QR code to user
-      console.log('MFA Setup:', { qrCode, secret });
-    } catch (error) {
-      console.error('MFA setup failed:', error);
-    }
-  };
-
-  const handleVerifyMFA = async (token: string) => {
-    try {
-      await verifyMFA(token);
-      console.log('MFA verified successfully');
-    } catch (error) {
-      console.error('MFA verification failed:', error);
-    }
-  };
+function PasswordInput() {
+  const [password, setPassword] = useState('');
+  const strength = calculatePasswordStrength(password);
 
   return (
     <div>
-      <button onClick={handleSetupMFA}>Setup MFA</button>
-      <input type="text" placeholder="Enter MFA token" />
-      <button onClick={() => handleVerifyMFA(token)}>Verify</button>
+      <input 
+        type="password" 
+        value={password}
+        onChange={(e) => setPassword(e.target.value)}
+      />
+      <div className={`strength-${strength.level}`}>
+        Strength: {strength.level} ({strength.score}/100)
+      </div>
+      {strength.feedback.length > 0 && (
+        <ul>
+          {strength.feedback.map((msg, i) => (
+            <li key={i}>{msg}</li>
+          ))}
+        </ul>
+      )}
     </div>
   );
 }
@@ -884,4 +890,51 @@ const soc2Utils = {
 - [ ] Data backup verification
 - [ ] Compliance monitoring
 
-For more information about implementing security in your application, see the [Authentication Guide](../core-concepts/authentication.md) and [RBAC System Guide](../core-concepts/rbac-system.md). 
+For more information about implementing security in your application, see the [Authentication Guide](../core-concepts/authentication.md) and [RBAC System Guide](../core-concepts/rbac-system.md).
+
+## ♿ Accessibility
+
+Security practices should maintain accessibility:
+
+- **Error messages are accessible** - Security errors should be clearly communicated
+- **Authentication flows are keyboard accessible** - All security forms should support keyboard navigation
+- **Screen reader support** - Security messages should be properly announced
+- **Focus management** - Ensure focus is properly managed during security operations
+- **Timeouts are announced** - Session timeouts should be accessible to screen readers
+
+### Accessibility Best Practices
+
+1. **Test authentication with screen readers** - Verify login flows work with assistive technologies
+2. **Ensure keyboard access** - All security forms should be keyboard accessible
+3. **Provide clear error messages** - Security errors should be descriptive without exposing vulnerabilities
+4. **Announce security state changes** - Use ARIA live regions for security status updates
+5. **Test with assistive technologies** - Verify all security features work with screen readers
+
+## ⚠️ Edge Cases
+
+### Security vs Usability Conflicts
+
+When security measures impact usability:
+- Find balance between security and user experience
+- Provide clear guidance for security requirements
+- Implement security transparently
+- Test with real users to ensure usability
+- Document security decisions
+
+### Rate Limiting Edge Cases
+
+When rate limiting causes issues:
+- Provide clear error messages for rate limit violations
+- Implement progressive backoff for retries
+- Consider user experience when setting limits
+- Monitor rate limit effectiveness
+- Adjust limits based on legitimate use patterns
+
+### Session Management Edge Cases
+
+When session management fails:
+- Handle session expiration gracefully
+- Provide clear messages for session issues
+- Ensure proper cleanup on session end
+- Test with multiple concurrent sessions
+- Verify session security across devices 

package/docs/best-practices/testing.md

@@ -1,14 +1,14 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T17:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Testing Best Practices
 
 Comprehensive testing is essential for maintaining code quality and preventing regressions. This guide provides testing strategies and patterns for `@jmruthers/pace-core` applications.
 
-> 📖 **For detailed testing standards and implementation patterns**, see the [Testing Standard](../../src/__tests__/TEST_STANDARD.md) - the authoritative guide for writing world-class tests in pace-core.
+> 📖 **For detailed testing standards and implementation patterns**, see the [Testing Standard](../standards/testing-standard.md) - the authoritative guide for writing world-class tests in pace-core.
 
 ## Overview
 
@@ -1002,4 +1002,33 @@ global.ResizeObserver = class ResizeObserver {
 - [ ] Test error announcements
 - [ ] Test skip links
 
+## ⚠️ Edge Cases
+
+### Testing Complex Scenarios
+
+When testing complex scenarios:
+- Test with realistic data volumes
+- Verify edge cases are covered
+- Test with different user roles and permissions
+- Ensure tests handle error conditions
+- Test with concurrent operations
+
+### Flaky Tests
+
+When tests are flaky:
+- Identify root causes of flakiness
+- Use proper wait strategies
+- Avoid timing-dependent tests
+- Mock external dependencies consistently
+- Document known flaky tests
+
+### Test Performance Issues
+
+When tests are slow:
+- Optimize test setup and teardown
+- Use test parallelization where possible
+- Mock expensive operations
+- Profile slow tests
+- Consider test prioritization
+
 For more information about testing your application, see the [Security Guide](./security.md) and [Performance Guide](./performance.md). 

package/docs/core-concepts/authentication.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T12:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Authentication
@@ -29,7 +29,7 @@ The authentication system provides:
 ```mermaid
 graph TD
     A[UnifiedAuthProvider] -->|Internal Services| B[AuthService]
-    A -->|Internal Services| C[RBACService]
+    A -->|RBAC Integration| C[RBAC Engine]
     A -->|Internal Services| D[OrganisationService]
     A -->|Internal Services| E[EventService]
     A -->|Internal Services| F[InactivityService]
@@ -121,7 +121,7 @@ sequenceDiagram
 
 ## What's Next?
 
-- **[Installation](../getting-started/installation.md)** - Get PACE Core set up
+- **[Installation](../getting-started/installation-guide.md)** - Get PACE Core set up
 - **[Quick Start](../getting-started/quick-start.md)** - Build your first app
 - **[RBAC System](./rbac-system.md)** - Understand role-based access control
 - **[Organisations](./organisations.md)** - Learn about multi-tenancy

package/docs/core-concepts/events.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T12:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Events

package/docs/core-concepts/organisations.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T12:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Organisations

package/docs/core-concepts/permissions.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T12:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Permissions

package/docs/core-concepts/rbac-system.md

@@ -1,12 +1,12 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T12:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # RBAC System
 
-> **📚 New Developer?** Start with the [Installation](../getting-started/installation.md) guide, then [Quick Start](../getting-started/quick-start.md) to build your first app.
+> **📚 New Developer?** Start with the [Installation](../getting-started/installation-guide.md) guide, then [Quick Start](../getting-started/quick-start.md) to build your first app.
 
 PACE Core provides a comprehensive Role-Based Access Control (RBAC) system that manages user permissions through roles, ensuring secure and scalable access control across your application.
 
@@ -287,7 +287,7 @@ For detailed migration instructions, see the **[RBAC Migration Guide](../migrati
 - **[RBAC API Reference](../rbac/api-reference.md)** - Complete API documentation
 - **[RBAC Examples](../rbac/examples.md)** - Practical usage examples
 - **[Migration Guide](../migration/rbac-migration.md)** - Migrate from legacy RBAC
-- **[Installation](../getting-started/installation.md)** - Get PACE Core set up
+- **[Installation](../getting-started/installation-guide.md)** - Get PACE Core set up
 - **[Authentication](./authentication.md)** - Understand authentication system
 - **[Organisations](./organisations.md)** - Learn about multi-tenancy
 - **[Events](./events.md)** - Understand event management

package/docs/documentation-index.md

@@ -5,10 +5,13 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 ## Getting started
 
 - [Installation guide](./getting-started/installation-guide.md) – package, peer dependency, and Tailwind setup.
+- [Quick start](./getting-started/quick-start.md) – get up and running quickly.
 - [Quick reference](./getting-started/quick-reference.md) – one page of common imports and commands.
-- [Vite configuration](./getting-started/consuming-app-vite-config.md) – include PACE Core sources when scanning Tailwind classes.
+- [Vite configuration](./getting-started/installation-guide.md#advanced-vite-configuration-options) – detailed Vite configuration options (see Installation Guide).
+- [Local development](./getting-started/local-development.md) – local development setup and workflows.
 - [FAQ](./getting-started/faq.md) – fast answers to onboarding questions.
 - [Getting started roadmap](./getting-started/documentation-index.md) – the task-by-task plan after installation.
+- [Examples](./getting-started/examples/) – complete working examples.
 
 ## Core concepts
 
@@ -25,6 +28,8 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [Providers](./api-reference/providers.md)
 - [Types](./api-reference/types.md)
 - [Utilities](./api-reference/utilities.md)
+- [RPC Functions](./api-reference/rpc-functions.md)
+- [Deprecated APIs](./api-reference/deprecated.md)
 
 ## Implementation guides
 
@@ -32,8 +37,12 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [App layout](./implementation-guides/app-layout.md)
 - [Component styling](./implementation-guides/component-styling.md)
 - [Data tables](./implementation-guides/data-tables.md)
+- [DataTable filtering](./implementation-guides/datatable-filtering.md)
+- [DataTable RBAC usage](./implementation-guides/datatable-rbac-usage.md)
+- [Hierarchical DataTable](./implementation-guides/hierarchical-datatable.md)
+- [Large datasets](./implementation-guides/large-datasets.md)
+- [Performance optimization](./implementation-guides/performance.md)
 - [Dynamic colours](./implementation-guides/dynamic-colors.md)
-- [Event theming summary](./implementation-guides/event-theming-summary.md)
 - [File reference system](./implementation-guides/file-reference-system.md)
 - [File upload & storage](./implementation-guides/file-upload-storage.md)
 - [Forms](./implementation-guides/forms.md)
@@ -42,20 +51,20 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [Organisation security](./implementation-guides/organisation-security.md)
 - [Permission enforcement](./implementation-guides/permission-enforcement.md)
 - [Public pages](./implementation-guides/public-pages.md)
-- [Public pages (advanced)](./implementation-guides/public-pages-advanced.md)
 
 ## RBAC module
 
 - [Overview](./rbac/README.md)
 - [Quick start](./rbac/quick-start.md)
+- [Event-based apps](./rbac/event-based-apps.md)
 - [Getting started](./rbac/getting-started.md)
 - [API reference](./rbac/api-reference.md)
 - [Examples](./rbac/examples.md)
+- [RLS integration example](./rbac/examples/rbac-rls-integration-example.md)
 - [Advanced patterns](./rbac/advanced-patterns.md)
 - [Super admin guide](./rbac/super-admin-guide.md)
 - [RLS integration](./rbac/rbac-rls-integration.md)
 - [Troubleshooting](./rbac/troubleshooting.md)
-- [Legacy RLS README](./rbac/README-rbac-rls-integration.md)
 
 ## Styling & theming
 
@@ -75,14 +84,19 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [Styling issues](./troubleshooting/styling-issues.md)
 - [Tailwind content scanning](./troubleshooting/tailwind-content-scanning.md)
 - [Organisation context setup](./troubleshooting/organisation-context-setup.md)
+- [Debugging](./troubleshooting/debugging.md)
+- [Migration issues](./troubleshooting/migration.md)
 - [Cake page permission guard issue summary](./troubleshooting/cake-page-permission-guard-issue-summary.md)
 - [Database view compatibility](./troubleshooting/database-view-compatibility.md)
 - [React hooks issue analysis](./troubleshooting/react-hooks-issue-analysis.md)
+- [Network error debugging](./troubleshooting/DEBUG_NETWORK_ERROR.md)
+- [Supabase CORS fix](./troubleshooting/FIX_SUPABASE_CORS.md)
 
 ## Migration & release notes
 
 - [Migration overview](./migration/README.md)
 - [Unified migration guide](./migration/MIGRATION_GUIDE.md)
+- [Quick migration guide](./migration/quick-migration-guide.md)
 - [Organisation context timing fix](./migration/organisation-context-timing-fix.md)
 - [Service architecture changes](./migration/service-architecture.md)
 - [RBAC migration](./migration/rbac-migration.md)
@@ -105,15 +119,23 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [Deployment](./best-practices/deployment.md)
 - [Performance](./best-practices/performance.md)
 - [Security](./best-practices/security.md)
-- [Testing](./best-practices/testing.md)
+- [Testing](./testing/README.md)
 
 ## Security
 
 - [Security posture](./security/README.md)
 - [Security checklist](./security/checklist.md)
 
+## Development standards
+
+- [Standards overview](./standards/README.md) – Development standards for the project
+- [Architecture Standard](./standards/01-architecture-standard.md) – Core architectural principles
+- [API & RPC Standard](./standards/02-api-and-rpc-standard.md) – API design patterns and database function standards
+- [Component Standard](./standards/03-component-standard.md) – React component development guidelines
+- [Code Style Standard](./standards/04-code-style-standard.md) – Code style and TypeScript conventions
+- [Security Standard](./standards/05-security-standard.md) – Security requirements and best practices
+- [Testing & Documentation Standard](./standards/06-testing-and-docs-standard.md) – Testing strategy and documentation requirements
+
 ## Meta & maintenance
 
-- [Documentation Standard](./DOCUMENTATION_STANDARD.md)
-- [Content audit report](./CONTENT_AUDIT_REPORT.md)
-- [Documentation audit notes](./DOCUMENTATION_AUDIT.md)
+- [Documentation index](./documentation-index.md) – This file

package/docs/getting-started/documentation-index.md

@@ -5,7 +5,7 @@ Follow this checklist after installing `@jmruthers/pace-core`. Each step points
 ## 1. Prepare the project
 
 - ✅ Install the package and peers → [Installation guide](./installation-guide.md)
-- ✅ Configure Tailwind scanning → [Consuming app Vite config](./consuming-app-vite-config.md)
+- ✅ Configure Tailwind scanning → [Installation guide - Vite Configuration](./installation-guide.md#advanced-vite-configuration-options)
 - ✅ Import base styles → [`@jmruthers/pace-core/styles/core.css`](../styles/README.md)
 
 ## 2. Connect authentication

package/docs/getting-started/examples/README.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T14:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # Examples & Starter Projects
@@ -562,7 +562,6 @@ function App() {
       <UnifiedAuthProvider 
         supabaseClient={supabase} 
         appName="meal-manager"
-        enableRBAC={true}
         requireOrganisationContext={true}
         idleTimeoutMs={30 * 60 * 1000}
         warnBeforeMs={5 * 60 * 1000}
@@ -880,8 +879,11 @@ Coming soon - complete starter projects you can download and run immediately:
 
 ### Component Examples
 
-See individual components in action:
+**Runnable Component Examples:**
+For importable, runnable TypeScript/React component examples, see:
+- [Runnable Examples](../../examples/) - Importable component examples (DataTable, Dialog, RBAC, PublicPages)
 
+**Component Documentation:**
 - [DataTable Examples](../api-reference/components.md#datatable)
 - [Form Examples](../api-reference/components.md#form)
 - [Navigation Examples](../implementation-guides/navigation.md)

package/docs/getting-started/examples/basic-auth-app.md

@@ -40,6 +40,9 @@ function App() {
     <UnifiedAuthProvider 
       supabaseClient={supabase} 
       appName="basic-auth-app"
+      idleTimeoutMs={30 * 60 * 1000} // 30 minutes
+      warnBeforeMs={5 * 60 * 1000} // 5 minutes warning
+      onIdleLogout={() => window.location.href = '/login'}
     >
       <BrowserRouter>
         <Routes>

package/docs/getting-started/examples/full-featured-app.md

@@ -68,12 +68,14 @@ import { AppRoutes } from './components/AppRoutes';
 function App() {
   return (
     <ErrorBoundary>
-      <UnifiedAuthProvider 
-        supabaseClient={supabase} 
+      <UnifiedAuthProvider
+        supabaseClient={supabase}
         appName="meal-manager"
-        enableRBAC={true}
         requireOrganisationContext={true}
         persistState={true}
+        idleTimeoutMs={30 * 60 * 1000} // 30 minutes
+        warnBeforeMs={5 * 60 * 1000} // 5 minutes warning
+        onIdleLogout={() => window.location.href = '/login'}
       >
         <OrganisationProvider>
           <EventProvider>

package/docs/getting-started/faq.md

@@ -1,7 +1,7 @@
 ---
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
+lastUpdated: 2025-11-18T14:00:00+11:00
+version: 0.5.181
+reviewedBy: documentation-standards-audit
 ---
 
 # PACE Core FAQ
@@ -14,7 +14,7 @@ Common questions and quick answers about PACE Core.
 
 ### How do I install PACE Core?
 
-See the [Installation Guide](./getting-started/installation-guide.md) for complete step-by-step instructions.
+See the [Installation Guide](./installation-guide.md) for complete step-by-step instructions.
 
 **Quick answer:**
 ```bash
@@ -57,7 +57,7 @@ npm install -D @tailwindcss/vite tailwindcss@^4.0.0
 npm uninstall tailwindcss@^3.0.0
 ```
 
-See [Installation Guide](./getting-started/installation-guide.md) for details.
+See [Installation Guide](./installation-guide.md) for details.
 
 ### Do I need a tailwind.config.js file?
 
@@ -193,7 +193,7 @@ See [RBAC Troubleshooting](./rbac/troubleshooting.md) for help.
 
 ### What are the coding standards?
 
-Follow the [Documentation Standard](../DOCUMENTATION_STANDARD.md) for:
+Follow the [Documentation Standard](../standards/README.md) for:
 - Code example standards
 - Terminology usage
 - Documentation structure