Feature/make castorix library

.cursor/rules/castorix-rules.mdc

@@ -0,0 +1,44 @@
+---
+description: Castorix project development rules and best practices
+globs:
+  - 'src/**/*.rs'
+  - 'tests/**/*.rs'
+  - '**/*.toml'
+  - '**/*.md'
+alwaysApply: true
+---
+
+# Castorix Project Rules
+
+You are an expert Rust developer working on the Castorix project, a Farcaster protocol integration tool.
+
+## Core Behaviors
+- After completing any significant task (bug fixes, feature implementation, CI/CD work, etc.), use `osascript` to notify the user
+- Use meaningful notification messages that summarize what was accomplished
+- Include relevant status indicators (✅ for success, ❌ for failures, etc.)
+- Always provide clear summaries of work completed
+
+## Code Quality Standards
+- Always run `cargo fmt` and `cargo clippy` before committing code
+- Ensure all tests pass before considering a task complete
+- Use descriptive commit messages that explain the changes made
+- Follow Rust naming conventions and best practices
+- Use proper error handling and logging throughout the codebase
+
+## Project-Specific Guidelines
+- This is a Rust project with Farcaster protocol integration
+- Tests should be cross-platform compatible (avoid hardcoded paths)
+- Use `get_castorix_binary()` helper function for test binary paths
+- Prefer editing existing files over creating new ones
+- Add all necessary import statements and dependencies
+
+## Communication Style
+- Explain technical decisions and their rationale
+- Use emojis appropriately to make output more readable
+- Always verify fixes work as expected before marking tasks complete
+- Provide actionable feedback and next steps when relevant
+
+## Error Handling
+- When tests fail, investigate the root cause before proposing fixes
+- For CI/CD issues, check both local and remote environment differences
+- Always run tests locally before pushing changes

.cursor/rules/ci-cd.mdc

@@ -0,0 +1,35 @@
+---
+description: CI/CD and deployment rules for Castorix
+globs:
+  - '.github/workflows/**/*.yml'
+  - '.github/workflows/**/*.yaml'
+  - 'Dockerfile*'
+  - 'docker-compose*.yml'
+alwaysApply: false
+---
+
+# CI/CD Rules
+
+## Pre-commit Checks
+- Run `cargo fmt --all -- --check`
+- Run `cargo clippy --all-targets --all-features -- -D warnings`
+- Run `cargo test --lib`
+- Check for TODO/FIXME comments in source code
+
+## GitHub Actions
+- Use latest stable Rust toolchain
+- Cache cargo dependencies for faster builds
+- Run tests in parallel when possible
+- Use meaningful job names and descriptions
+
+## Testing Strategy
+- Unit tests must pass locally before pushing
+- Integration tests should be robust and handle network failures
+- Use environment variables for test configuration
+- Skip tests that require external services when appropriate
+
+## Release Process
+- Tag releases with semantic versioning
+- Update CHANGELOG.md for each release
+- Build and test release binaries
+- Verify all features work in release mode

.cursor/rules/notification.mdc

@@ -0,0 +1,28 @@
+---
+description: Task completion notification requirements for Castorix project
+alwaysApply: false
+---
+
+# Task Completion Notifications
+
+## Core Requirement
+- After completing any significant task (bug fixes, feature implementation, CI/CD work, etc.), ALWAYS use `osascript` to notify the user
+- This is a critical requirement that must be followed for every completed task
+
+## Notification Format
+Use the following osascript command format:
+```bash
+osascript -e 'display notification "✅ [Task Summary]" with title "Castorix [Category]" sound name "Glass"'
+```
+
+## Examples
+- ✅ CI errors fixed and code committed
+- ✅ Feature implementation completed
+- ✅ Bug fix deployed successfully
+- ❌ Task failed - requires attention
+
+## Status Indicators
+- Use ✅ for successful completion
+- Use ❌ for failures or errors
+- Use 🔧 for ongoing work or maintenance
+- Use 🚀 for new features or releases

.cursor/rules/rust-standards.mdc

@@ -0,0 +1,33 @@
+---
+description: Rust coding standards and best practices for Castorix
+globs:
+  - 'src/**/*.rs'
+  - 'tests/**/*.rs'
+  - 'benches/**/*.rs'
+alwaysApply: false
+---
+
+# Rust Standards
+
+## Code Formatting
+- Always run `cargo fmt` before committing
+- Use `cargo clippy` with `-D warnings` flag
+- Follow standard Rust naming conventions (snake_case for functions/variables, PascalCase for types)
+
+## Testing
+- Write comprehensive unit tests for all public functions
+- Use `get_castorix_binary()` helper for integration tests
+- Ensure cross-platform compatibility in tests
+- Run `cargo test --all-features` before committing
+
+## Error Handling
+- Use `anyhow::Result<T>` for error handling
+- Provide meaningful error messages
+- Log errors appropriately using the `log` crate
+- Handle network errors gracefully
+
+## Performance
+- Avoid unnecessary allocations
+- Use `&str` instead of `String` when possible
+- Consider using `Cow<str>` for string handling
+- Profile performance-critical code

.github/workflows/pr-simple.yml

@@ -0,0 +1,99 @@
+name: PR Simple Tests
+
+on:
+  pull_request:
+    branches: [master, main]
+    types: [opened, synchronize, reopened]
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  pr-tests:
+    name: PR Tests
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: actions-rs/toolchain@v1
+        with:
+          toolchain: stable
+          components: rustfmt, clippy
+          override: true
+
+      - name: Install nightly Rust with rustfmt
+        run: rustup toolchain install nightly --component rustfmt
+
+      - name: Install Foundry
+        uses: foundry-rs/foundry-toolchain@v1
+        with:
+          version: nightly
+
+      - name: Cache dependencies
+        uses: actions/cache@v3
+        with:
+          path: |
+            ~/.cargo/registry
+            ~/.cargo/git
+            target
+          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
+
+      - name: Initialize contracts submodule
+        run: |
+          if [ -f "contracts/.git" ]; then
+            echo "Contracts submodule already initialized"
+          else
+            echo "Initializing contracts submodule..."
+            git submodule update --init --recursive contracts || echo "Warning: Failed to initialize contracts submodule"
+          fi
+
+      - name: Build project first (to generate required files)
+        run: cargo build --all-features
+
+      - name: Check formatting
+        run: cargo +nightly fmt --all -- --check
+
+      - name: Run clippy
+        run: cargo clippy --all-targets --all-features
+
+
+      - name: Run unit tests
+        run: cargo test --lib
+
+      - name: Run integration tests
+        run: cargo test --test "*"
+
+      - name: Test CLI commands
+        run: |
+          cargo run --bin castorix -- --help
+          cargo run --bin castorix -- key --help
+          cargo run --bin castorix -- fid --help
+          cargo run --bin castorix -- storage --help
+          cargo run --bin castorix -- ens --help
+          cargo run --bin start-node -- --help
+
+      - name: Check for TODO/FIXME comments
+        run: |
+          echo "🔍 Checking for TODO/FIXME comments..."
+          if grep -r "TODO\|FIXME\|XXX\|HACK" src/ --include="*.rs"; then
+            echo "⚠️ Found TODO/FIXME comments in source code:"
+            grep -r "TODO\|FIXME\|XXX\|HACK" src/ --include="*.rs" || true
+            echo "Please review and address these comments before merging."
+          else
+            echo "✅ No TODO/FIXME comments found in source code"
+          fi
+
+      - name: Generate test summary
+        run: |
+          echo "## PR Test Results ✅" >> $GITHUB_STEP_SUMMARY
+          echo "- **Build**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **Formatting**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **Clippy**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **Unit Tests**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **Integration Tests**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **CLI Tests**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "- **Code Quality**: ✅ Passed" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "🎉 All tests passed! Ready for review." >> $GITHUB_STEP_SUMMARY