fraim-framework 2.0.30 → 2.0.34

package/registry/rules/ephemeral-execution.md

@@ -1,47 +1,57 @@
-# Rule: Ephemeral Script Execution
+# Rule: Direct Script Execution
 
-To maintain repository cleanliness, all automation scripts provided by FRAIM must be executed ephemerally.
+FRAIM scripts are pre-synchronized to the user's local directory and executed directly from there.
 
 ## Policy
 
-1.  **No Persistence**: Do NOT save FRAIM scripts (e.g., `.sh`, `.ts`, `.py`) to the local repository or any directory tracked by version control.
-2.  **Temporary Storage**: Use the `.fraim/tmp` directory in the user's home folder for script execution.
-    *   Windows: `%USERPROFILE%\.fraim\tmp`
-    *   Linux/macOS: `~/.fraim/tmp`
-3.  **Execute and Delete**: Immediately delete the script file after execution, regardless of whether the script succeeded or failed.
+1. **Pre-Synchronized Scripts**: All FRAIM scripts are automatically synced to `~/.fraim/scripts/` during `fraim init` and `fraim sync`.
+2. **Direct Execution**: Execute scripts directly from the user scripts directory using standard shell commands.
+3. **No Fetching Required**: Scripts are already available locally - no need to fetch from MCP server.
 
-## Directory Creation
+## Script Location
 
-If the `.fraim/tmp` directory does not exist, it should be created before saving the script.
+Scripts are located in the user's home directory:
+- **Windows**: `%USERPROFILE%\.fraim\scripts\`
+- **Linux/macOS**: `~/.fraim/scripts/`
 
 ## Implementation Pattern
 
-When a script is retrieved from the FRAIM MCP:
+When a script is needed:
 
-1.  **Identify**: Recognize the file as an executable script.
-2.  **Locate OS Temp**: Determine the appropriate temporary path.
-3.  **Transfer**: Write the script content to a file in the temporary path with a unique name (e.g., `fraim_task_123.sh`).
-4.  **Execute**: Run the script from that temporary location.
-5.  **Clean up**: Remove the temporary file.
+1. **Verify Sync**: Ensure scripts are up to date with `fraim sync` if needed
+2. **Execute Directly**: Run the script from its synced location
+3. **Working Directory**: Scripts operate on the current working directory
 
 ## Example (Bash)
 
 ```bash
-# Get script content from MCP (simulated)
-SCRIPT_CONTENT=$(mcp_call get_fraim_file path="scripts/setup.sh")
+# Execute script directly from synced location
+~/.fraim/scripts/prep-issue.sh 123
 
-# Save to temp
-FRAIM_TMP="$HOME/.fraim/tmp"
-mkdir -p "$FRAIM_TMP"
-TEMP_FILE=$(mktemp "$FRAIM_TMP/fraim_script.XXXXXX.sh")
-echo "$SCRIPT_CONTENT" > "$TEMP_FILE"
+# Or with full path on Windows
+%USERPROFILE%\.fraim\scripts\prep-issue.sh 123
 
-# Execute
-bash "$TEMP_FILE"
+# TypeScript scripts
+npx tsx ~/.fraim/scripts/generate-engagement-emails.ts
+```
+
+## Example (Node.js/JavaScript)
+
+```javascript
+// Execute script using child_process
+const { execSync } = require('child_process');
+const os = require('os');
+const path = require('path');
+
+const scriptsDir = path.join(os.homedir(), '.fraim', 'scripts');
+const scriptPath = path.join(scriptsDir, 'prep-issue.sh');
 
-# Delete
-rm "$TEMP_FILE"
+// Execute script
+execSync(`"${scriptPath}" 123`, { 
+    cwd: process.cwd(),  // Current working directory
+    stdio: 'inherit' 
+});
 ```
 
 > [!IMPORTANT]
-> This rule is mandatory for all coding agents interacting with this repository.
+> This rule replaces the previous ephemeral execution pattern. Scripts are now treated as pre-installed tools rather than dynamic content.

package/registry/rules/local-development.md

@@ -1,252 +1,254 @@
-# Local Development Guidelines
-
-## INTENT
-Enable safe parallel development through strict workspace separation, preventing conflicts between agents and maintaining code integrity.
-
-## PRINCIPLES
-- **Workspace Isolation**: Each agent works in their own cloned repository folder
-- **Branch Discipline**: Always work on feature branches, never push to master
-- **Timeout Management**: Use exec-with-timeout for all commands to prevent hangs
-- **Coordination**: Use GitHub issues and PRs for agent communication
-
-## CORE RULES
-
-### Development Environment
-- Use local file system for development work in your own cloned repository folder
-- Push to feature branches only; never push to master
-- Do NOT open PRs; push and let Actions open/update Draft PRs
-- Always work in your own cloned repository folder.
-All your work **MUST** be in your folder.
-- Coordinate with other agents through GitHub issues and PRs
-- Each agent works independently in their own folder to enable true parallel development
-- Run every command using `npx tsx tmp/exec-with-timeout.ts --timeout 30 -- <your command>` (Retrieve script via `get_fraim_file({ path: "scripts/exec-with-timeout.ts" })`)
-
-## CRITICAL RULE: Absolute Workspace Separation
-
-### Main Workspace: READ-ONLY
-- **Directory**: `{PROJECT_NAME}` (no issue number)
-- **Purpose**: Reference only - for reading existing code
-- **PROHIBITION**: **NEVER** create, edit, or modify ANY files here
-
-### Local Clone: WORK-ONLY  
-- **Directory**: `{PROJECT_NAME} - Issue {issue_number}` (includes issue number)
-- **Purpose**: All development work happens here exclusively
-- **Rule**: ALL file operations must be within this directory
-
-## WORKSPACE OPERATIONS
-
-### Safe Operations (READ-ONLY)
-- `read_file()` from main workspace for reference
-- `grep_search()` in main workspace for analysis
-- `list_dir()` in main workspace for exploration
-- `find_by_name()` in main workspace for discovery
-
-### Work Operations (LOCAL CLONE ONLY)
-- `edit_file()` - ONLY in your local clone
-- `write_to_file()` - ONLY in your local clone
-- `delete_file()` - ONLY in your local clone
-- All git operations - ONLY in your local clone
-
-### NEVER Use These Patterns:
-```
-❌ edit_file("{PROJECT_NAME}/...")           # Main workspace
-❌ edit_file("../{PROJECT_NAME}/...")        # Main workspace via relative path
-❌ edit_file(".windsurf/...")                    # Main workspace config
-❌ Any path containing main workspace name
-```
-
-### ALWAYS Use These Patterns:
-```
-✅ edit_file("src/...")                      # Relative path in local clone
-✅ edit_file("./src/...")                    # Explicit relative path
-✅ read_file("../{PROJECT_NAME}/src/...")    # Reference main workspace
-✅ Working directory check before operations
-```
-
-## COMMAND EXECUTION
-
-### Timeout Wrapper (MANDATORY)
-ALL commands must use the timeout wrapper:
-
-```bash
-# Standard timeout (30 seconds)
-npx tsx tmp/exec-with-timeout.ts --timeout 30 -- npm install
-
-# Extended timeout for long operations
-npx tsx tmp/exec-with-timeout.ts --timeout 300 -- npm run build
-
-# Very long operations (tests, servers)
-npx tsx tmp/exec-with-timeout.ts --timeout 1800 -- npm run test-all
-```
-
-### Timeout Guidelines
-- **Quick commands**: 30 seconds (npm install, git operations)
-- **Build operations**: 300 seconds (5 minutes)
-- **Test suites**: 1800 seconds (30 minutes)
-- **Development servers**: 3600 seconds (1 hour)
-
-## DIRECTORY STRUCTURE RULES
-
-### Correct Naming Convention:
-- **Main Workspace**: `{PROJECT_NAME}` (READ-ONLY)
-- **Local Clone**: `{PROJECT_NAME} - Issue {issue_number}` (WORK HERE)
-
-**The issue number in directory name is a visual reminder you're in the right place.**
-
-### Directory Verification
-Before ANY file operation, verify you're in the correct directory:
-
-```bash
-# Check current directory
-pwd
-
-# Verify you're in local clone (should contain issue number)
-basename "$(pwd)" | grep -q "Issue [0-9]"
-```
-
-## BRANCH MANAGEMENT
-
-### Branch Naming Convention
-- Format: `feature/{issue_number}-{kebab-case-title}`
-- Example: `feature/123-fix-authentication-bug`
-- Always include issue number for traceability
-
-### Branch Operations
-```bash
-# Create and switch to feature branch
-git checkout -b feature/123-fix-authentication-bug
-
-# Push branch to origin
-git push -u origin feature/123-fix-authentication-bug
-
-# Never push to master
-git push origin master  # ❌ FORBIDDEN
-```
-
-## COORDINATION PATTERNS
-
-### Agent Communication
-- Use GitHub issues for task coordination
-- Use PR comments for code review feedback
-- Use issue labels for status tracking
-- Never directly modify another agent's work
-
-### Status Updates
-- Update issue labels to reflect current phase
-- Add comments to issues with progress updates
-- Link PRs to issues for traceability
-- Use draft PRs for work-in-progress
-
-## SAFETY CHECKS
-
-### Pre-Operation Verification
-1. **Directory Check**: Confirm you're in local clone
-2. **Branch Check**: Confirm you're on feature branch
-3. **File Path Check**: Confirm relative paths only
-4. **Timeout Check**: Confirm command has timeout wrapper
-
-### Example Verification Script
-```bash
-# Verify safe working environment
-CURRENT_DIR=$(basename "$(pwd)")
-CURRENT_BRANCH=$(git branch --show-current)
-
-if [[ ! "$CURRENT_DIR" =~ "Issue [0-9]+" ]]; then
-    echo "❌ Not in local clone directory"
-    exit 1
-fi
-
-if [[ "$CURRENT_BRANCH" == "master" ]] || [[ "$CURRENT_BRANCH" == "main" ]]; then
-    echo "❌ Working on main branch"
-    exit 1
-fi
-
-echo "✅ Safe working environment confirmed"
-```
-
-## TESTING PATTERNS
-
-### Mock Service Pattern
-**Use mocks to isolate components during testing**
-
-**Example**:
-```typescript
-const mockApiService = {
-  calls: [],
-  updateResource: async (request) => {
-    mockApiService.calls.push({ method: 'updateResource', request });
-    return { success: true };
-  }
-};
-
-// After running action, validate calls
-const updateCall = mockApiService.calls.find(call => call.method === 'updateResource');
-if (!updateCall) throw new Error('Expected updateResource to be called');
-if (updateCall.request.resourceId !== expectedId) throw new Error('Wrong resource ID');
-```
-
-## EXAMPLES
-
-### Good: Proper Workspace Usage
-```
-✅ Working Directory: /path/to/{PROJECT_NAME} - Issue 84
-✅ File Operation: edit_file("src/api-service.ts")
-✅ Branch Check: feature/84-fix-api-sync
-✅ Path Verification: Relative path, no "../" patterns
-✅ Command: npx tsx scripts/exec-with-timeout.ts --timeout 30 -- npm test
-```
-
-### Bad: Workspace Violations
-```
-❌ Working Directory: /path/to/{PROJECT_NAME} (main workspace)
-❌ File Operation: edit_file("src/api-service.ts")
-❌ Branch Check: main
-❌ Path Verification: Working in main workspace
-❌ Command: npm test (no timeout wrapper)
-```
-
-### Good: Reference Operations
-```
-✅ Read from main workspace: read_file("../{PROJECT_NAME}/docs/README.md")
-✅ Search main workspace: grep("api", "../{PROJECT_NAME}/src/")
-✅ List main workspace: list_dir("../{PROJECT_NAME}/")
-Result: Safe reference without modification
-```
-
-### Bad: Modification in Main Workspace
-```
-❌ Edit main workspace: edit_file("../{PROJECT_NAME}/src/api-service.ts")
-❌ Delete main workspace: delete_file("../{PROJECT_NAME}/test-file.ts")
-❌ Search replace main: search_replace("../{PROJECT_NAME}/...")
-Result: Violates workspace separation
-```
-
-## CLEANUP
-
-### End of Work Session
-When work is complete, clean up your local clone:
-
-```bash
-# Navigate out of local clone
-cd ..
-
-# Remove your local clone folder
-rm -rf "{PROJECT_NAME} - Issue {issue_number}"
-```
-
-## TROUBLESHOOTING
-
-### Common Issues
-1. **Permission Denied**: Check if you're in the right directory
-2. **Git Conflicts**: Ensure you're on feature branch, not master
-3. **Command Hangs**: Always use timeout wrapper
-4. **File Not Found**: Verify relative paths and working directory
-
-### Recovery Steps
-1. Stop all running processes
-2. Navigate to correct local clone directory
-3. Check git status and current branch
-4. Verify file paths are relative
-5. Use timeout wrapper for all commands
-
+# Local Development Guidelines
+
+## INTENT
+Enable safe parallel development through strict workspace separation, preventing conflicts between agents and maintaining code integrity.
+
+## PRINCIPLES
+- **Workspace Isolation**: Each agent works in their own cloned repository folder
+- **Branch Discipline**: Always work on feature branches, never push to master
+- **Timeout Management**: Use exec-with-timeout for all commands to prevent hangs
+- **Coordination**: Use GitHub issues and PRs for agent communication
+
+## CORE RULES
+
+### Development Environment
+- Use local file system for development work in your own cloned repository folder
+- Push to feature branches only; never push to master
+- Do NOT open PRs; push and let Actions open/update Draft PRs
+- Always work in your own cloned repository folder.
+All your work **MUST** be in your folder.
+- Coordinate with other agents through GitHub issues and PRs
+- Each agent works independently in their own folder to enable true parallel development
+- Run every command using `npx tsx ~/.fraim/scripts/exec-with-timeout.ts --timeout 30 -- <your command>` (Script is pre-synced)
+
+## CRITICAL RULE: Absolute Workspace Separation
+
+### Main Workspace: READ-ONLY
+- **Directory**: `{PROJECT_NAME}` (no issue number)
+- **Purpose**: Reference only - for reading existing code
+- **PROHIBITION**: **NEVER** create, edit, or modify ANY files here
+
+### Local Clone: WORK-ONLY  
+- **Directory**: `{PROJECT_NAME} - Issue {issue_number}` (includes issue number)
+- **Purpose**: All development work happens here exclusively
+- **Rule**: ALL file operations must be within this directory
+
+## WORKSPACE OPERATIONS
+
+### Safe Operations (READ-ONLY)
+- `read_file()` from main workspace for reference
+- `grep_search()` in main workspace for analysis
+- `list_dir()` in main workspace for exploration
+- `find_by_name()` in main workspace for discovery
+
+### Work Operations (LOCAL CLONE ONLY)
+- `edit_file()` - ONLY in your local clone
+- `write_to_file()` - ONLY in your local clone
+- `delete_file()` - ONLY in your local clone
+- All git operations - ONLY in your local clone
+
+### NEVER Use These Patterns:
+```
+❌ edit_file("{PROJECT_NAME}/...")           # Main workspace
+❌ edit_file("../{PROJECT_NAME}/...")        # Main workspace via relative path
+❌ edit_file(".windsurf/...")                    # Main workspace config
+❌ Any path containing main workspace name
+```
+
+### ALWAYS Use These Patterns:
+```
+✅ edit_file("src/...")                      # Relative path in local clone
+✅ edit_file("./src/...")                    # Explicit relative path
+✅ read_file("../{PROJECT_NAME}/src/...")    # Reference main workspace
+✅ Working directory check before operations
+```
+
+## COMMAND EXECUTION
+
+### Timeout Wrapper (MANDATORY)
+ALL commands must use the timeout wrapper:
+
+```bash
+# Standard timeout (30 seconds)
+npx tsx ~/.fraim/scripts/exec-with-timeout.ts --timeout 30 -- npm install
+
+# Extended timeout for long operations
+npx tsx ~/.fraim/scripts/exec-with-timeout.ts --timeout 300 -- npm run build
+
+# Very long operations (tests, servers)
+npx tsx ~/.fraim/scripts/exec-with-timeout.ts --timeout 1800 -- npm run test-all
+
+# On Windows, use %USERPROFILE% instead of ~
+```
+
+### Timeout Guidelines
+- **Quick commands**: 30 seconds (npm install, git operations)
+- **Build operations**: 300 seconds (5 minutes)
+- **Test suites**: 1800 seconds (30 minutes)
+- **Development servers**: 3600 seconds (1 hour)
+
+## DIRECTORY STRUCTURE RULES
+
+### Correct Naming Convention:
+- **Main Workspace**: `{PROJECT_NAME}` (READ-ONLY)
+- **Local Clone**: `{PROJECT_NAME} - Issue {issue_number}` (WORK HERE)
+
+**The issue number in directory name is a visual reminder you're in the right place.**
+
+### Directory Verification
+Before ANY file operation, verify you're in the correct directory:
+
+```bash
+# Check current directory
+pwd
+
+# Verify you're in local clone (should contain issue number)
+basename "$(pwd)" | grep -q "Issue [0-9]"
+```
+
+## BRANCH MANAGEMENT
+
+### Branch Naming Convention
+- Format: `feature/{issue_number}-{kebab-case-title}`
+- Example: `feature/123-fix-authentication-bug`
+- Always include issue number for traceability
+
+### Branch Operations
+```bash
+# Create and switch to feature branch
+git checkout -b feature/123-fix-authentication-bug
+
+# Push branch to origin
+git push -u origin feature/123-fix-authentication-bug
+
+# Never push to master
+git push origin master  # ❌ FORBIDDEN
+```
+
+## COORDINATION PATTERNS
+
+### Agent Communication
+- Use GitHub issues for task coordination
+- Use PR comments for code review feedback
+- Use issue labels for status tracking
+- Never directly modify another agent's work
+
+### Status Updates
+- Update issue labels to reflect current phase
+- Add comments to issues with progress updates
+- Link PRs to issues for traceability
+- Use draft PRs for work-in-progress
+
+## SAFETY CHECKS
+
+### Pre-Operation Verification
+1. **Directory Check**: Confirm you're in local clone
+2. **Branch Check**: Confirm you're on feature branch
+3. **File Path Check**: Confirm relative paths only
+4. **Timeout Check**: Confirm command has timeout wrapper
+
+### Example Verification Script
+```bash
+# Verify safe working environment
+CURRENT_DIR=$(basename "$(pwd)")
+CURRENT_BRANCH=$(git branch --show-current)
+
+if [[ ! "$CURRENT_DIR" =~ "Issue [0-9]+" ]]; then
+    echo "❌ Not in local clone directory"
+    exit 1
+fi
+
+if [[ "$CURRENT_BRANCH" == "master" ]] || [[ "$CURRENT_BRANCH" == "main" ]]; then
+    echo "❌ Working on main branch"
+    exit 1
+fi
+
+echo "✅ Safe working environment confirmed"
+```
+
+## TESTING PATTERNS
+
+### Mock Service Pattern
+**Use mocks to isolate components during testing**
+
+**Example**:
+```typescript
+const mockApiService = {
+  calls: [],
+  updateResource: async (request) => {
+    mockApiService.calls.push({ method: 'updateResource', request });
+    return { success: true };
+  }
+};
+
+// After running action, validate calls
+const updateCall = mockApiService.calls.find(call => call.method === 'updateResource');
+if (!updateCall) throw new Error('Expected updateResource to be called');
+if (updateCall.request.resourceId !== expectedId) throw new Error('Wrong resource ID');
+```
+
+## EXAMPLES
+
+### Good: Proper Workspace Usage
+```
+✅ Working Directory: /path/to/{PROJECT_NAME} - Issue 84
+✅ File Operation: edit_file("src/api-service.ts")
+✅ Branch Check: feature/84-fix-api-sync
+✅ Path Verification: Relative path, no "../" patterns
+✅ Command: npx tsx scripts/exec-with-timeout.ts --timeout 30 -- npm test
+```
+
+### Bad: Workspace Violations
+```
+❌ Working Directory: /path/to/{PROJECT_NAME} (main workspace)
+❌ File Operation: edit_file("src/api-service.ts")
+❌ Branch Check: main
+❌ Path Verification: Working in main workspace
+❌ Command: npm test (no timeout wrapper)
+```
+
+### Good: Reference Operations
+```
+✅ Read from main workspace: read_file("../{PROJECT_NAME}/docs/README.md")
+✅ Search main workspace: grep("api", "../{PROJECT_NAME}/src/")
+✅ List main workspace: list_dir("../{PROJECT_NAME}/")
+Result: Safe reference without modification
+```
+
+### Bad: Modification in Main Workspace
+```
+❌ Edit main workspace: edit_file("../{PROJECT_NAME}/src/api-service.ts")
+❌ Delete main workspace: delete_file("../{PROJECT_NAME}/test-file.ts")
+❌ Search replace main: search_replace("../{PROJECT_NAME}/...")
+Result: Violates workspace separation
+```
+
+## CLEANUP
+
+### End of Work Session
+When work is complete, clean up your local clone:
+
+```bash
+# Navigate out of local clone
+cd ..
+
+# Remove your local clone folder
+rm -rf "{PROJECT_NAME} - Issue {issue_number}"
+```
+
+## TROUBLESHOOTING
+
+### Common Issues
+1. **Permission Denied**: Check if you're in the right directory
+2. **Git Conflicts**: Ensure you're on feature branch, not master
+3. **Command Hangs**: Always use timeout wrapper
+4. **File Not Found**: Verify relative paths and working directory
+
+### Recovery Steps
+1. Stop all running processes
+2. Navigate to correct local clone directory
+3. Check git status and current branch
+4. Verify file paths are relative
+5. Use timeout wrapper for all commands
+
 Respect CODEOWNERS; don't modify auth/CI without approval.