@jmruthers/pace-core 0.6.5 → 0.6.7

package/docs/api-reference/rpc-functions.md

@@ -162,12 +162,87 @@ Documented in [RBAC API Reference](../rbac/api-reference.md):
 
 ### Event System
 
-- `data_user_events_get` - Get events accessible to a user (replaces deprecated `get_pace_user_events`)
-- `get_public_event_by_code` - Get public event by code (public access, exception to naming pattern)
+- `data_user_events_get` - Get events accessible to a user
 - `data_event_list` - List events (if implemented)
 - `app_event_create` - Create an event (if implemented)
 
-**Note**: `get_public_event_by_code` is a legacy function that doesn't follow the standard naming pattern. It's maintained for backward compatibility with public pages.
+**Note**: For public event access, use `usePublicEvent()` hook from pace-core, which handles direct table queries internally.
+
+## Removed Legacy RPC Functions
+
+The following RPC functions have been **removed** in v0.6.x. All consuming apps have been migrated to modern alternatives.
+
+### Removed Functions (v0.6.x)
+
+#### `get_pace_user_events` → `data_user_events_get` or `useEvents()` hook
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Use `data_user_events_get` RPC or `useEvents()` hook from pace-core
+
+#### `get_public_event_by_code` → Direct table queries or `usePublicEvent()` hook
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Use `usePublicEvent()` hook from pace-core (handles direct table queries internally)
+
+#### `get_public_event_logo` → Direct table queries or `usePublicEventLogo()` hook
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Use `usePublicEventLogo()` hook from pace-core (handles direct table queries internally)
+
+#### `get_organisation_members` → Direct table queries or `data_user_organisation_roles_get`
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Query `rbac_organisation_roles` table directly or use `data_user_organisation_roles_get` RPC
+
+#### `set_organisation_context` → No longer needed
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Organisation context is now handled automatically via secure Supabase client headers (`useSecureSupabase()` hook)
+
+#### `get_organisation_context` → No longer used
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Not needed - context is handled via secure client
+
+#### `get_page_scope_type` → Direct table queries
+
+**Status**: Removed in v0.6.x  
+**Replacement**: Query `rbac_app_pages.scope_type` directly
+
+**Migration Guide**: See [Deprecated Functions Documentation](./deprecated.md#legacy-event-rpcs) for detailed migration paths.
+
+### Internal Infrastructure Functions (pace-core Only)
+
+These functions are used internally by pace-core and should **NOT** be called directly by consuming apps:  
+**Modern Alternative**: Use `usePublicEvent` hook from pace-core
+
+**Action Required**: If calling directly, migrate to `usePublicEvent` hook. If using pace-core hooks, no action needed.
+
+#### `get_public_event_logo`
+
+**Status**: Legacy (exception to naming standard)  
+**Usage**: Public pages only (no authentication required)  
+**Modern Alternative**: Use `usePublicEventLogo` hook from pace-core
+
+**Action Required**: If calling directly, migrate to `usePublicEventLogo` hook. If using pace-core hooks, no action needed.
+
+### Internal Infrastructure Functions (pace-core Only)
+
+**Removed Functions** (v0.6.x):
+- ~~`set_organisation_context`~~ - **REMOVED** - Organisation context now handled via secure client headers
+- ~~`get_organisation_context`~~ - **REMOVED** - No longer needed
+- ~~`get_page_scope_type`~~ - **REMOVED** - Replaced with direct table queries
+
+**Active Functions** (pace-core internal, do not call directly):
+- `grant_event_app_role` - Used by `useRoleManagement` hook (use hook instead)
+
+**Note**: The removed functions have been replaced with direct table queries or are no longer needed. Organisation context is automatically handled by the secure Supabase client from `useSecureSupabase()` hook.
+
+### Migration Resources
+
+- **Legacy RPC Audit Prompt**: `packages/core/audit/legacy-rpc-audit-prompt.md` - Run this in your consuming app to identify usage
+- **Deprecated Functions Guide**: [Deprecated Functions Documentation](./deprecated.md) - Detailed migration guides
+- **Migration Examples**: See migration guides in `packages/core/docs/migration/`
 
 ## Application-Specific RPCs
 

package/docs/api-reference/types.md

@@ -1048,7 +1048,7 @@ All types in `@jmruthers/pace-core` are designed to provide:
 - **Generic Support**: Flexible types that work with your data
 - **Strict Mode**: Compatible with TypeScript strict mode
 
-For more information about using types effectively, see the [TypeScript Guide](../best-practices/typescript.md).
+For more information about using types effectively, see the [Code Quality Standards](../standards/4-code-quality-standards.md) (TypeScript rules).
 
 ## ♿ Accessibility
 

package/docs/api-reference/utilities.md

@@ -1204,7 +1204,7 @@ export {
 - Validate input parameters
 - Return consistent types
 
-For more information about using utilities effectively, see the [Best Practices Guide](../best-practices/utilities.md).
+For more information about using utilities effectively, see the [Code Quality Standards](../standards/4-code-quality-standards.md) and [Architecture Standards](../standards/3-architecture-standards.md).
 
 ## ♿ Accessibility
 

package/docs/architecture/README.md

@@ -125,7 +125,7 @@ ComponentName/
 
 ### Component Design Patterns
 
-1. **Compound Components**: Components that work together (e.g., DataTable + DataTableToolbar + DataTableBody)
+1. **Compound Components**: Components that work together (e.g., DataTable + DataTableToolbar + UnifiedTableBody)
 2. **Render Props**: Flexible rendering patterns for complex components
 3. **Controlled/Uncontrolled**: Support for both controlled and uncontrolled usage
 4. **Composition**: Components that can be composed together

package/docs/core-concepts/events.md

@@ -273,7 +273,7 @@ function EventScopedData() {
   }, [selectedEvent]);
 
   if (!selectedEvent) {
-    return <div>Please select an event</div>;
+    return <p>Please select an event</p>;
   }
 
   if (loading) {
@@ -585,10 +585,10 @@ function EventScopedComponent() {
   const { selectedEvent } = useEvents();
 
   if (!selectedEvent) {
-    return <div>Please select an event</div>;
+    return <p>Please select an event</p>;
   }
 
-  return <div>Content for {selectedEvent.event_name}</div>;
+  return <section>Content for {selectedEvent.event_name}</section>;
 }
 
 // ❌ Avoid - No event context check

package/docs/core-concepts/organisations.md

@@ -514,8 +514,8 @@ function OrganisationAwareComponent() {
     updateOrganisationSettings,
   } = useOrganisation();
 
-  if (loading) return <div>Loading...</div>;
-  if (error) return <div>Error: {error}</div>;
+  if (loading) return <p>Loading...</p>;
+  if (error) return <p>Error: {error}</p>;
 
   return (
     <div>
@@ -563,10 +563,10 @@ function ProtectedComponent() {
   );
 
   if (!hasAccess) {
-    return <div>Access denied</div>;
+    return <p>Access denied</p>;
   }
 
-  return <div>Protected content</div>;
+  return <section>Protected content</section>;
 }
 ```
 
@@ -598,10 +598,10 @@ function DataComponent() {
   const { currentOrganisation } = useOrganisation();
 
   if (!currentOrganisation) {
-    return <div>Please select an organisation</div>;
+    return <p>Please select an organisation</p>;
   }
 
-  return <div>Organisation data</div>;
+  return <section>Organisation data</section>;
 }
 ```
 

package/docs/core-concepts/permissions.md

@@ -210,8 +210,8 @@ import { usePagePermission } from '@jmruthers/pace-core';
 function AdminDashboard() {
   const { hasAccess, loading } = usePagePermission('admin');
 
-  if (loading) return <div>Checking permissions...</div>;
-  if (!hasAccess) return <div>Access denied</div>;
+  if (loading) return <p>Checking permissions...</p>;
+  if (!hasAccess) return <p>Access denied</p>;
 
   return (
     <div>
@@ -305,7 +305,7 @@ function ProtectedComponent({ children, permission }) {
     permission
   );
 
-  if (isLoading) return <div>Checking permissions...</div>;
+  if (isLoading) return <p>Checking permissions...</p>;
   if (!can) return null; // Or return an access denied component
 
   return children;
@@ -488,7 +488,7 @@ function withPermission(permission: string) {
         permission
       );
       
-      if (isLoading) return <div>Checking permissions...</div>;
+      if (isLoading) return <p>Checking permissions...</p>;
       if (!can) return null;
       
       return <Component {...props} />;
@@ -547,7 +547,7 @@ function PermissionAwareComponent() {
   );
 
   if (isLoading) {
-    return <div>Loading permissions...</div>;
+    return <p>Loading permissions...</p>;
   }
 
   return (
@@ -714,7 +714,7 @@ function FeatureFlag({ permission, children }) {
     permission
   );
   
-  if (isLoading) return <div>Checking permissions...</div>;
+  if (isLoading) return <p>Checking permissions...</p>;
   if (!can) return null;
   
   return children;

package/docs/documentation-index.md

@@ -109,30 +109,24 @@ This index mirrors the folder layout in `packages/core/docs/` so teams can quick
 - [RBAC security architecture](./architecture/rbac-security-architecture.md)
 - [Database schema requirements](./architecture/database-schema-requirements.md)
 
-## Best practices
-
-- [Overview](./best-practices/README.md)
-- [Accessibility](./best-practices/accessibility.md)
-- [Common patterns](./best-practices/common-patterns.md)
-- [Deployment](./best-practices/deployment.md)
-- [Performance](./best-practices/performance.md)
-- [Security](./best-practices/security.md)
-- [Testing](./testing/README.md)
+## Standards
+
+- [Standards Overview](./standards/0-standards-overview.md) – Complete standards system
+- [pace-core Compliance](./standards/1-pace-core-compliance-standards.md) – Using pace-core correctly
+- [Project Structure](./standards/2-project-structure-standards.md) – Code organization
+- [Architecture](./standards/3-architecture-standards.md) – SOLID principles and design
+- [Code Quality](./standards/4-code-quality-standards.md) – TypeScript, accessibility, and code style
+- [Styling](./standards/5-styling-standards.md) – CSS architecture and Tailwind v4
+- [Security & RBAC](./standards/6-security-rbac-standards.md) – RLS policies and RBAC
+- [API & Tech Stack](./standards/7-api-tech-stack-standards.md) – Required technologies and API design
+- [Testing & Documentation](./standards/8-testing-documentation-standards.md) – Testing strategy and docs
+- [Operations](./standards/9-operations-standards.md) – Error handling, performance, CI/CD
 
 ## 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
 

package/docs/getting-started/cursor-rules.md

@@ -128,25 +128,6 @@ Content with examples and guidelines.
 
 ## Running Audits
 
-### Comprehensive Audit
-
-Run the comprehensive audit tool to check compliance:
-
-```bash
-node node_modules/@jmruthers/pace-core/scripts/audit-consuming-app.cjs
-```
-
-Or add to your `package.json`:
-
-```json
-{
-  "scripts": {
-    "audit:pace-core": "node node_modules/@jmruthers/pace-core/scripts/audit-consuming-app.cjs"
-  }
-}
-```
-
-This generates a timestamped markdown report in `audit/` directory.
 
 ### Compliance Check
 
@@ -237,10 +218,9 @@ Each app maintains its own `.cursor/rules/` directory.
    - Explicitly reference rules when needed: "Follow rules 00-04"
 
 3. **Before Committing:**
-   ```bash
-   npm run audit:pace-core
-   ```
-   Review the generated report in `audit/` directory
+   - Run linting and type checks
+   - Run tests
+   - Review code changes
 
 4. **After pace-core Updates:**
    ```bash