@jmruthers/pace-core 0.5.191 → 0.6.1

package/cursor-rules/CHANGELOG.md

@@ -0,0 +1,101 @@
+# Cursor Rules Changelog
+
+All notable changes to pace-core cursor rules will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- Initial release of cursor rules system
+- 8 comprehensive rule files covering compliance, standards, structure, SOLID, testing, bug reports, code quality, and tech stack
+- Installation script with safety guards
+- Comprehensive audit tool with Phase 1 (deterministic) and Phase 2 (heuristic) checks
+- Markdown report generation with timestamps
+
+## [1.0.0] - 2025-01-15
+
+### Added
+- **00-pace-core-compliance.mdc** - Enforces pace-core usage patterns
+- **01-standards-compliance.mdc** - Maps to all pace-core standards
+- **02-project-structure.mdc** - Defines standard folder structure
+- **03-solid-principles.mdc** - Enforces SOLID architecture principles
+- **04-testing-standards.mdc** - Enforces testing framework consistency
+- **05-bug-reports-and-features.mdc** - Templates for bug reports and feature requests
+- **06-code-quality.mdc** - Enforces code quality standards
+- **07-tech-stack-compliance.mdc** - Enforces tech stack versions and patterns
+
+### Features
+- Opt-in installation script (not automatic postinstall)
+- Safety guards (environment variable, git check)
+- Version tracking in rule files
+- Rule numbering system (pace-core: 00-09, apps: 50+)
+- Targeted globs for efficient rule application
+- MUST/SHOULD/MAY semantics for clear guidance
+- Comprehensive audit tool with markdown reports
+- Phase-based audit approach (deterministic vs heuristic)
+
+### Documentation
+- README.md with installation and usage guide
+- Getting started guide in docs
+- Updated standards README with cursor rules section
+
+## Migration Guide
+
+### From No Rules to Cursor Rules
+
+1. Install pace-core (if not already installed):
+   ```bash
+   npm install @jmruthers/pace-core
+   ```
+
+2. Install cursor rules:
+   ```bash
+   node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs
+   ```
+
+3. Restart Cursor to load rules
+
+4. Run audit to check compliance:
+   ```bash
+   node node_modules/@jmruthers/pace-core/scripts/audit-consuming-app.cjs
+   ```
+
+### Updating Rules
+
+When pace-core is updated:
+
+1. Update pace-core:
+   ```bash
+   npm update @jmruthers/pace-core
+   ```
+
+2. Update rules:
+   ```bash
+   npm run setup:cursor-rules
+   ```
+
+3. Review any changes in rule files
+
+### Custom Rules
+
+If you have custom rules, number them starting at 50:
+- `50-my-custom-rule.mdc`
+- `51-another-rule.mdc`
+- etc.
+
+This ensures pace-core rules (00-09) load first.
+
+## Version History
+
+- **1.0.0** (2025-01-15) - Initial release
+
+## Future Enhancements
+
+Potential future enhancements:
+- CLI for rule validation
+- GitHub Action template for PR audits
+- Rule update notification system
+- Interactive rule configuration
+- Rule effectiveness metrics

package/cursor-rules/README.md

@@ -0,0 +1,191 @@
+# pace-core Cursor Rules
+
+This directory contains Cursor rules that ensure consuming apps maintain quality, consistency, and compliance with pace-core standards.
+
+## What are Cursor Rules?
+
+Cursor rules are `.mdc` (Markdown Cursor) files that guide AI assistants (like Cursor) to follow specific patterns and standards when writing code. These rules are automatically loaded by Cursor when present in `.cursor/rules/` directory.
+
+## Installation
+
+### Automatic Installation (Recommended)
+
+Run the installation script from your consuming app root:
+
+```bash
+node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs
+```
+
+Or add to your `package.json`:
+
+```json
+{
+  "scripts": {
+    "setup:cursor-rules": "node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs"
+  }
+}
+```
+
+Then run:
+
+```bash
+npm run setup:cursor-rules
+```
+
+### Manual Installation
+
+Copy all `.mdc` files from `node_modules/@jmruthers/pace-core/cursor-rules/` to your `.cursor/rules/` directory.
+
+## Rule Files
+
+The rules are numbered for ordering (00-07):
+
+- **00-pace-core-compliance.mdc** - Enforce pace-core usage patterns
+- **01-standards-compliance.mdc** - Enforce all pace-core standards
+- **02-project-structure.mdc** - Define standard folder structure
+- **03-solid-principles.mdc** - Enforce SOLID architecture principles
+- **04-testing-standards.mdc** - Enforce testing framework consistency
+- **05-bug-reports-and-features.mdc** - Templates for bug reports and feature requests (guidance-only)
+- **06-code-quality.mdc** - Enforce code quality standards
+- **07-tech-stack-compliance.mdc** - Enforce tech stack versions and patterns
+
+## Rule Numbering System
+
+- **pace-core rules**: `00-09` (reserved for pace-core)
+- **Your app rules**: `50+` (create your own rules starting at 50)
+
+This ensures pace-core rules load first, and your custom rules load after.
+
+## Customization
+
+### Adding Your Own Rules
+
+Create your own rules in `.cursor/rules/` with numbers starting at `50`:
+
+```
+.cursor/rules/
+├── 00-pace-core-compliance.mdc      # pace-core rule
+├── 01-standards-compliance.mdc     # pace-core rule
+├── ...
+├── 50-my-custom-rule.mdc           # Your custom rule
+└── 51-another-custom-rule.mdc      # Your custom rule
+```
+
+### Updating Rules
+
+When pace-core is updated, run the installation script again. The script will:
+- **Automatically update** pace-core rules (00-09) if they've changed (version or content differs)
+- Preserve your custom rules (50+)
+- Skip files that are already up to date
+
+### Force Update
+
+To force update all rules (even when versions match):
+
+```bash
+node node_modules/@jmruthers/pace-core/scripts/install-cursor-rules.cjs --force
+```
+
+**Note**: Normally, pace-core rules (00-09) are automatically updated when they change. The `--force` flag forces an update even when versions match (useful if content changed but version metadata wasn't updated).
+
+## How Cursor Uses Rules
+
+Cursor automatically loads all `.mdc` files from `.cursor/rules/` when:
+- You open a file that matches the rule's `globs` pattern
+- You ask Cursor to write or modify code
+- Cursor needs context for code generation
+
+Rules with `alwaysApply: true` are always considered, while rules with `alwaysApply: false` are only referenced when relevant.
+
+## Explicitly Referencing Rules
+
+When working with Cursor, you can explicitly reference rules:
+
+> "Use pace-core components and follow rules 00–04."
+
+This helps Cursor focus on specific rule sets.
+
+## Rule Format
+
+Each rule file follows this format:
+
+```markdown
+---
+description: Brief description
+globs: ["targeted/path/**/*.{ts,tsx}"]  # Files this rule applies to
+alwaysApply: true  # or false
+paceCoreVersion: "0.5.x"  # pace-core version
+rulesVersion: "2025-01-15"  # Rule update date
+---
+
+# Rule Title
+
+Content with examples and guidelines.
+```
+
+## Safety Guards
+
+The installation script includes safety guards:
+
+- **Environment variable**: Set `PACE_CURSOR_RULES_DISABLED=1` to skip installation
+- **Git check**: Skips if no `.git` folder exists (CI/safety)
+- **Auto-update**: Automatically updates pace-core rules (00-09) when they change
+- **Protection**: Never overwrites custom app rules (50+)
+
+## Monorepo Support
+
+For monorepos, run the installation script from each app's root directory. Each app maintains its own `.cursor/rules/` directory.
+
+## Troubleshooting
+
+### Rules Not Loading
+
+1. Verify rules are in `.cursor/rules/` directory
+2. Check file extensions are `.mdc`
+3. Restart Cursor if rules were just installed
+4. Check rule frontmatter is valid YAML
+
+### Rules Conflicting
+
+1. Check rule numbering (pace-core: 00-09, yours: 50+)
+2. Verify `globs` patterns don't overlap unnecessarily
+3. Review rule priorities in frontmatter
+
+### Installation Fails
+
+1. Check you're in the app root directory
+2. Verify `node_modules/@jmruthers/pace-core/` exists
+3. Check file permissions
+4. Try with `--force` flag if needed
+
+## Audit Tool
+
+Run the audit tool to check compliance:
+
+```bash
+node node_modules/@jmruthers/pace-core/scripts/audit-consuming-app.cjs
+```
+
+This generates a timestamped markdown report in `audit/` directory.
+
+## Version Tracking
+
+Each rule file includes version metadata:
+- `paceCoreVersion`: pace-core version these rules target
+- `rulesVersion`: Date when rules were last updated
+
+Check these to see if rules need updating.
+
+## Related Documentation
+
+- [pace-core Standards](../docs/standards/README.md)
+- [Getting Started Guide](../docs/getting-started/cursor-rules.md)
+- [pace-core Exports](../docs/api-reference/README.md)
+
+## Support
+
+For issues with cursor rules:
+1. Check this README
+2. Review rule files for guidance
+3. File an issue in pace-core repository
+4. Check pace-core documentation

package/dist/{AuthService-CbP_utw2.d.ts → AuthService-DjnJHDtC.d.ts}

@@ -203,6 +203,7 @@ declare class OrganisationService extends BaseService implements IOrganisationSe
     private _roleMapState;
     private _isLoading;
     private _error;
+    private _isSuperAdmin;
     private _isContextReady;
     private retryCount;
     private supabaseClient;

package/dist/{DataTable-Be6dH_dR.d.ts → DataTable-CH1U5Tpy.d.ts}

@@ -101,7 +101,7 @@ interface DataTableProps<TData extends DataRecord> {
     /** Whether the table is in a loading state */
     isLoading?: boolean;
     /** Custom component to display when table is empty */
-    emptyState?: EmptyStateConfig | React__default.ReactElement;
+    emptyState?: EmptyStateConfig | React__default.ReactElement<any>;
     /** Array of aggregation functions for grouped data */
     aggregates?: AggregateConfig[];
     /** Import modal configuration */

package/dist/{DataTable-WKRZD47S.js → DataTable-DQ7RSOHE.js}

@@ -60,8 +60,8 @@ import {
   sum,
   validateHierarchicalData,
   validatePaginationConfig
-} from "./chunk-ULHIJK66.js";
-import "./chunk-VRGWKHDB.js";
+} from "./chunk-T33XF5ZC.js";
+import "./chunk-XM25TVIE.js";
 import {
   CircuitBreaker,
   DEFAULT_FALLBACK_CONFIG,
@@ -79,10 +79,11 @@ import {
   safeExecute,
   throttle,
   useDataTablePerformance
-} from "./chunk-6C4YBBJM.js";
-import "./chunk-OETXORNB.js";
-import "./chunk-6LTQQAT6.js";
-import "./chunk-ROXMHMY2.js";
+} from "./chunk-3QRJFVBR.js";
+import "./chunk-3XTALGJF.js";
+import "./chunk-KQCRWDSA.js";
+import "./chunk-BYFSK72L.js";
+import "./chunk-KNC55RTG.js";
 import "./chunk-63FOKYGO.js";
 import "./chunk-QXHPKYJV.js";
 import "./chunk-R77UEZ4E.js";
@@ -169,4 +170,4 @@ export {
   validateHierarchicalData,
   validatePaginationConfig
 };
-//# sourceMappingURL=DataTable-WKRZD47S.js.map
+//# sourceMappingURL=DataTable-DQ7RSOHE.js.map