bmalph 1.0.0 → 2.2.1

package/ralph/ralph_monitor.sh

@@ -0,0 +1,125 @@
+#!/bin/bash
+
+# Ralph Status Monitor - Live terminal dashboard for the Ralph loop
+set -e
+
+STATUS_FILE=".ralph/status.json"
+LOG_FILE=".ralph/logs/ralph.log"
+REFRESH_INTERVAL=2
+
+# Colors
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+PURPLE='\033[0;35m'
+CYAN='\033[0;36m'
+WHITE='\033[1;37m'
+NC='\033[0m'
+
+# Clear screen and hide cursor
+clear_screen() {
+    clear
+    printf '\033[?25l'  # Hide cursor
+}
+
+# Show cursor on exit
+show_cursor() {
+    printf '\033[?25h'  # Show cursor
+}
+
+# Cleanup function
+cleanup() {
+    show_cursor
+    echo
+    echo "Monitor stopped."
+    exit 0
+}
+
+# Set up signal handlers
+trap cleanup SIGINT SIGTERM EXIT
+
+# Main display function
+display_status() {
+    clear_screen
+    
+    # Header
+    echo -e "${WHITE}╔════════════════════════════════════════════════════════════════════════╗${NC}"
+    echo -e "${WHITE}║                           🤖 RALPH MONITOR                              ║${NC}"
+    echo -e "${WHITE}║                        Live Status Dashboard                           ║${NC}"
+    echo -e "${WHITE}╚════════════════════════════════════════════════════════════════════════╝${NC}"
+    echo
+    
+    # Status section
+    if [[ -f "$STATUS_FILE" ]]; then
+        # Parse JSON status
+        local status_data=$(cat "$STATUS_FILE")
+        local loop_count=$(echo "$status_data" | jq -r '.loop_count // "0"' 2>/dev/null || echo "0")
+        local calls_made=$(echo "$status_data" | jq -r '.calls_made_this_hour // "0"' 2>/dev/null || echo "0")
+        local max_calls=$(echo "$status_data" | jq -r '.max_calls_per_hour // "100"' 2>/dev/null || echo "100")
+        local status=$(echo "$status_data" | jq -r '.status // "unknown"' 2>/dev/null || echo "unknown")
+        
+        echo -e "${CYAN}┌─ Current Status ────────────────────────────────────────────────────────┐${NC}"
+        echo -e "${CYAN}│${NC} Loop Count:     ${WHITE}#$loop_count${NC}"
+        echo -e "${CYAN}│${NC} Status:         ${GREEN}$status${NC}"
+        echo -e "${CYAN}│${NC} API Calls:      $calls_made/$max_calls"
+        echo -e "${CYAN}└─────────────────────────────────────────────────────────────────────────┘${NC}"
+        echo
+        
+    else
+        echo -e "${RED}┌─ Status ────────────────────────────────────────────────────────────────┐${NC}"
+        echo -e "${RED}│${NC} Status file not found. Ralph may not be running."
+        echo -e "${RED}└─────────────────────────────────────────────────────────────────────────┘${NC}"
+        echo
+    fi
+    
+    # Claude Code Progress section
+    if [[ -f ".ralph/progress.json" ]]; then
+        local progress_data=$(cat ".ralph/progress.json" 2>/dev/null)
+        local progress_status=$(echo "$progress_data" | jq -r '.status // "idle"' 2>/dev/null || echo "idle")
+        
+        if [[ "$progress_status" == "executing" ]]; then
+            local indicator=$(echo "$progress_data" | jq -r '.indicator // "⠋"' 2>/dev/null || echo "⠋")
+            local elapsed=$(echo "$progress_data" | jq -r '.elapsed_seconds // "0"' 2>/dev/null || echo "0")
+            local last_output=$(echo "$progress_data" | jq -r '.last_output // ""' 2>/dev/null || echo "")
+            
+            echo -e "${YELLOW}┌─ Claude Code Progress ──────────────────────────────────────────────────┐${NC}"
+            echo -e "${YELLOW}│${NC} Status:         ${indicator} Working (${elapsed}s elapsed)"
+            if [[ -n "$last_output" && "$last_output" != "" ]]; then
+                # Truncate long output for display
+                local display_output=$(echo "$last_output" | head -c 60)
+                echo -e "${YELLOW}│${NC} Output:         ${display_output}..."
+            fi
+            echo -e "${YELLOW}└─────────────────────────────────────────────────────────────────────────┘${NC}"
+            echo
+        fi
+    fi
+    
+    # Recent logs
+    echo -e "${BLUE}┌─ Recent Activity ───────────────────────────────────────────────────────┐${NC}"
+    if [[ -f "$LOG_FILE" ]]; then
+        tail -n 8 "$LOG_FILE" | while IFS= read -r line; do
+            echo -e "${BLUE}│${NC} $line"
+        done
+    else
+        echo -e "${BLUE}│${NC} No log file found"
+    fi
+    echo -e "${BLUE}└─────────────────────────────────────────────────────────────────────────┘${NC}"
+    
+    # Footer
+    echo
+    echo -e "${YELLOW}Controls: Ctrl+C to exit | Refreshes every ${REFRESH_INTERVAL}s | $(date '+%H:%M:%S')${NC}"
+}
+
+# Main monitor loop
+main() {
+    echo "Starting Ralph Monitor..."
+    sleep 2
+    
+    while true; do
+        display_status
+        sleep "$REFRESH_INTERVAL"
+    done
+}
+
+main

package/ralph/templates/AGENT.md

@@ -1,158 +1,158 @@
-# Agent Build Instructions
-
-## Project Setup
-```bash
-# Install dependencies (example for Node.js project)
-npm install
-
-# Or for Python project
-pip install -r requirements.txt
-
-# Or for Rust project  
-cargo build
-```
-
-## Running Tests
-```bash
-# Node.js
-npm test
-
-# Python
-pytest
-
-# Rust
-cargo test
-```
-
-## Build Commands
-```bash
-# Production build
-npm run build
-# or
-cargo build --release
-```
-
-## Development Server
-```bash
-# Start development server
-npm run dev
-# or
-cargo run
-```
-
-## Key Learnings
-- Update this section when you learn new build optimizations
-- Document any gotchas or special setup requirements
-- Keep track of the fastest test/build cycle
-
-## Feature Development Quality Standards
-
-**CRITICAL**: All new features MUST meet the following mandatory requirements before being considered complete.
-
-### Testing Requirements
-
-- **Minimum Coverage**: 85% code coverage ratio required for all new code
-- **Test Pass Rate**: 100% - all tests must pass, no exceptions
-- **Test Types Required**:
-  - Unit tests for all business logic and services
-  - Integration tests for API endpoints or main functionality
-  - End-to-end tests for critical user workflows
-- **Coverage Validation**: Run coverage reports before marking features complete:
-  ```bash
-  # Examples by language/framework
-  npm run test:coverage
-  pytest --cov=src tests/ --cov-report=term-missing
-  cargo tarpaulin --out Html
-  ```
-- **Test Quality**: Tests must validate behavior, not just achieve coverage metrics
-- **Test Documentation**: Complex test scenarios must include comments explaining the test strategy
-
-### Git Workflow Requirements
-
-Before moving to the next feature, ALL changes must be:
-
-1. **Committed with Clear Messages**:
-   ```bash
-   git add .
-   git commit -m "feat(module): descriptive message following conventional commits"
-   ```
-   - Use conventional commit format: `feat:`, `fix:`, `docs:`, `test:`, `refactor:`, etc.
-   - Include scope when applicable: `feat(api):`, `fix(ui):`, `test(auth):`
-   - Write descriptive messages that explain WHAT changed and WHY
-
-2. **Pushed to Remote Repository**:
-   ```bash
-   git push origin <branch-name>
-   ```
-   - Never leave completed features uncommitted
-   - Push regularly to maintain backup and enable collaboration
-   - Ensure CI/CD pipelines pass before considering feature complete
-
-3. **Branch Hygiene**:
-   - Work on feature branches, never directly on `main`
-   - Branch naming convention: `feature/<feature-name>`, `fix/<issue-name>`, `docs/<doc-update>`
-   - Create pull requests for all significant changes
-
-4. **Ralph Integration**:
-   - Update .ralph/@fix_plan.md with new tasks before starting work
-   - Mark items complete in .ralph/@fix_plan.md upon completion
-   - Update .ralph/PROMPT.md if development patterns change
-   - Test features work within Ralph's autonomous loop
-
-### Documentation Requirements
-
-**ALL implementation documentation MUST remain synchronized with the codebase**:
-
-1. **Code Documentation**:
-   - Language-appropriate documentation (JSDoc, docstrings, etc.)
-   - Update inline comments when implementation changes
-   - Remove outdated comments immediately
-
-2. **Implementation Documentation**:
-   - Update relevant sections in this AGENT.md file
-   - Keep build and test commands current
-   - Update configuration examples when defaults change
-   - Document breaking changes prominently
-
-3. **README Updates**:
-   - Keep feature lists current
-   - Update setup instructions when dependencies change
-   - Maintain accurate command examples
-   - Update version compatibility information
-
-4. **AGENT.md Maintenance**:
-   - Add new build patterns to relevant sections
-   - Update "Key Learnings" with new insights
-   - Keep command examples accurate and tested
-   - Document new testing patterns or quality gates
-
-### Feature Completion Checklist
-
-Before marking ANY feature as complete, verify:
-
-- [ ] All tests pass with appropriate framework command
-- [ ] Code coverage meets 85% minimum threshold
-- [ ] Coverage report reviewed for meaningful test quality
-- [ ] Code formatted according to project standards
-- [ ] Type checking passes (if applicable)
-- [ ] All changes committed with conventional commit messages
-- [ ] All commits pushed to remote repository
-- [ ] .ralph/@fix_plan.md task marked as complete
-- [ ] Implementation documentation updated
-- [ ] Inline code comments updated or added
-- [ ] .ralph/@AGENT.md updated (if new patterns introduced)
-- [ ] Breaking changes documented
-- [ ] Features tested within Ralph loop (if applicable)
-- [ ] CI/CD pipeline passes
-
-### Rationale
-
-These standards ensure:
-- **Quality**: High test coverage and pass rates prevent regressions
-- **Traceability**: Git commits and .ralph/@fix_plan.md provide clear history of changes
-- **Maintainability**: Current documentation reduces onboarding time and prevents knowledge loss
-- **Collaboration**: Pushed changes enable team visibility and code review
-- **Reliability**: Consistent quality gates maintain production stability
-- **Automation**: Ralph integration ensures continuous development practices
-
-**Enforcement**: AI agents should automatically apply these standards to all feature development tasks without requiring explicit instruction for each task.
+# Agent Build Instructions
+
+## Project Setup
+```bash
+# Install dependencies (example for Node.js project)
+npm install
+
+# Or for Python project
+pip install -r requirements.txt
+
+# Or for Rust project  
+cargo build
+```
+
+## Running Tests
+```bash
+# Node.js
+npm test
+
+# Python
+pytest
+
+# Rust
+cargo test
+```
+
+## Build Commands
+```bash
+# Production build
+npm run build
+# or
+cargo build --release
+```
+
+## Development Server
+```bash
+# Start development server
+npm run dev
+# or
+cargo run
+```
+
+## Key Learnings
+- Update this section when you learn new build optimizations
+- Document any gotchas or special setup requirements
+- Keep track of the fastest test/build cycle
+
+## Feature Development Quality Standards
+
+**CRITICAL**: All new features MUST meet the following mandatory requirements before being considered complete.
+
+### Testing Requirements
+
+- **Minimum Coverage**: 85% code coverage ratio required for all new code
+- **Test Pass Rate**: 100% - all tests must pass, no exceptions
+- **Test Types Required**:
+  - Unit tests for all business logic and services
+  - Integration tests for API endpoints or main functionality
+  - End-to-end tests for critical user workflows
+- **Coverage Validation**: Run coverage reports before marking features complete:
+  ```bash
+  # Examples by language/framework
+  npm run test:coverage
+  pytest --cov=src tests/ --cov-report=term-missing
+  cargo tarpaulin --out Html
+  ```
+- **Test Quality**: Tests must validate behavior, not just achieve coverage metrics
+- **Test Documentation**: Complex test scenarios must include comments explaining the test strategy
+
+### Git Workflow Requirements
+
+Before moving to the next feature, ALL changes must be:
+
+1. **Committed with Clear Messages**:
+   ```bash
+   git add .
+   git commit -m "feat(module): descriptive message following conventional commits"
+   ```
+   - Use conventional commit format: `feat:`, `fix:`, `docs:`, `test:`, `refactor:`, etc.
+   - Include scope when applicable: `feat(api):`, `fix(ui):`, `test(auth):`
+   - Write descriptive messages that explain WHAT changed and WHY
+
+2. **Pushed to Remote Repository**:
+   ```bash
+   git push origin <branch-name>
+   ```
+   - Never leave completed features uncommitted
+   - Push regularly to maintain backup and enable collaboration
+   - Ensure CI/CD pipelines pass before considering feature complete
+
+3. **Branch Hygiene**:
+   - Work on feature branches, never directly on `main`
+   - Branch naming convention: `feature/<feature-name>`, `fix/<issue-name>`, `docs/<doc-update>`
+   - Create pull requests for all significant changes
+
+4. **Ralph Integration**:
+   - Update .ralph/fix_plan.md with new tasks before starting work
+   - Mark items complete in .ralph/fix_plan.md upon completion
+   - Update .ralph/PROMPT.md if development patterns change
+   - Test features work within Ralph's autonomous loop
+
+### Documentation Requirements
+
+**ALL implementation documentation MUST remain synchronized with the codebase**:
+
+1. **Code Documentation**:
+   - Language-appropriate documentation (JSDoc, docstrings, etc.)
+   - Update inline comments when implementation changes
+   - Remove outdated comments immediately
+
+2. **Implementation Documentation**:
+   - Update relevant sections in this AGENT.md file
+   - Keep build and test commands current
+   - Update configuration examples when defaults change
+   - Document breaking changes prominently
+
+3. **README Updates**:
+   - Keep feature lists current
+   - Update setup instructions when dependencies change
+   - Maintain accurate command examples
+   - Update version compatibility information
+
+4. **AGENT.md Maintenance**:
+   - Add new build patterns to relevant sections
+   - Update "Key Learnings" with new insights
+   - Keep command examples accurate and tested
+   - Document new testing patterns or quality gates
+
+### Feature Completion Checklist
+
+Before marking ANY feature as complete, verify:
+
+- [ ] All tests pass with appropriate framework command
+- [ ] Code coverage meets 85% minimum threshold
+- [ ] Coverage report reviewed for meaningful test quality
+- [ ] Code formatted according to project standards
+- [ ] Type checking passes (if applicable)
+- [ ] All changes committed with conventional commit messages
+- [ ] All commits pushed to remote repository
+- [ ] .ralph/fix_plan.md task marked as complete
+- [ ] Implementation documentation updated
+- [ ] Inline code comments updated or added
+- [ ] .ralph/AGENT.md updated (if new patterns introduced)
+- [ ] Breaking changes documented
+- [ ] Features tested within Ralph loop (if applicable)
+- [ ] CI/CD pipeline passes
+
+### Rationale
+
+These standards ensure:
+- **Quality**: High test coverage and pass rates prevent regressions
+- **Traceability**: Git commits and .ralph/fix_plan.md provide clear history of changes
+- **Maintainability**: Current documentation reduces onboarding time and prevents knowledge loss
+- **Collaboration**: Pushed changes enable team visibility and code review
+- **Reliability**: Consistent quality gates maintain production stability
+- **Automation**: Ralph integration ensures continuous development practices
+
+**Enforcement**: AI agents should automatically apply these standards to all feature development tasks without requiring explicit instruction for each task.