aidp 0.7.0 → 0.8.0

data/lib/aidp/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Aidp
-  VERSION = "0.7.0"
+  VERSION = "0.8.0"
 end

data/lib/aidp.rb

@@ -1,50 +1,65 @@
 # frozen_string_literal: true
 
 # Core extensions
-require "aidp/core_ext/class_attribute"
+require_relative "aidp/core_ext/class_attribute"
 
 # Shared modules
-require "aidp/version"
-require "aidp/config"
-require "aidp/workspace"
-require "aidp/util"
-require "aidp/cli"
-require "aidp/cli/jobs_command"
-require "aidp/project_detector"
-require "aidp/sync"
-
-# Database
-require "aidp/database_connection"
-
-# Job infrastructure
-require "aidp/job_manager"
-require "aidp/jobs/base_job"
-require "aidp/jobs/provider_execution_job"
+require_relative "aidp/version"
+require_relative "aidp/config"
+require_relative "aidp/util"
+require_relative "aidp/cli"
+require_relative "aidp/cli/jobs_command"
 
 # Providers
-require "aidp/providers/base"
-require "aidp/providers/cursor"
-require "aidp/providers/anthropic"
-require "aidp/providers/gemini"
-require "aidp/providers/macos_ui"
-require "aidp/provider_manager"
-
-# Analyze mode
-require "aidp/analyze/error_handler"
-require "aidp/analyze/parallel_processor"
-require "aidp/analyze/repository_chunker"
-require "aidp/analyze/ruby_maat_integration"
-require "aidp/analyze/runner"
-require "aidp/analyze/steps"
-require "aidp/analyze/progress"
+require_relative "aidp/providers/base"
+require_relative "aidp/providers/cursor"
+require_relative "aidp/providers/anthropic"
+require_relative "aidp/providers/gemini"
+require_relative "aidp/providers/macos_ui"
+# Supervised providers removed - using direct execution model
+require_relative "aidp/provider_manager"
+
+# Simple file-based storage
+require_relative "aidp/storage/json_storage"
+require_relative "aidp/storage/csv_storage"
+require_relative "aidp/storage/file_manager"
+
+# Analyze mode (simplified - file-based storage only)
+require_relative "aidp/analyze/json_file_storage"
+require_relative "aidp/analyze/error_handler"
+require_relative "aidp/analyze/ruby_maat_integration"
+require_relative "aidp/analyze/runner"
+require_relative "aidp/analyze/steps"
+require_relative "aidp/analyze/progress"
 
 # Tree-sitter analysis
-require "aidp/analysis/tree_sitter_grammar_loader"
-require "aidp/analysis/seams"
-require "aidp/analysis/tree_sitter_scan"
-require "aidp/analysis/kb_inspector"
+require_relative "aidp/analysis/tree_sitter_grammar_loader"
+require_relative "aidp/analysis/seams"
+require_relative "aidp/analysis/tree_sitter_scan"
+require_relative "aidp/analysis/kb_inspector"
 
 # Execute mode
-require "aidp/execute/steps"
-require "aidp/execute/runner"
-require "aidp/execute/progress"
+require_relative "aidp/execute/steps"
+require_relative "aidp/execute/runner"
+require_relative "aidp/execute/progress"
+
+# Harness mode
+require_relative "aidp/harness/configuration"
+require_relative "aidp/harness/config_schema"
+require_relative "aidp/harness/config_validator"
+require_relative "aidp/harness/config_loader"
+require_relative "aidp/harness/config_manager"
+require_relative "aidp/harness/condition_detector"
+require_relative "aidp/harness/user_interface"
+require_relative "aidp/harness/provider_manager"
+require_relative "aidp/harness/provider_config"
+require_relative "aidp/harness/provider_factory"
+require_relative "aidp/harness/state_manager"
+require_relative "aidp/harness/error_handler"
+require_relative "aidp/harness/status_display"
+require_relative "aidp/harness/runner"
+
+# UI components
+require_relative "aidp/harness/ui/spinner_helper"
+
+# CLI commands

data/templates/COMMON/AGENT_BASE.md

@@ -20,6 +20,17 @@ This template provides common capabilities and guidelines for AI agents in both
 - **Contextual Relevance**: Ensure recommendations are relevant to the project
 - **Professional Tone**: Maintain a helpful, professional demeanor
 
+### User Interaction Guidelines
+
+#### TUI-Based Interaction
+
+- **Interactive Questions**: Present questions through the harness TUI system for real-time user input
+- **Validation**: Use built-in validation for user responses (required fields, format validation, etc.)
+- **Error Handling**: Provide clear error messages and allow users to correct invalid input
+- **Progress Feedback**: Show progress indicators and status updates during long operations
+- **Rich Interface**: Utilize CLI UI components for beautiful, interactive terminal experience
+- **STDOUT Integration**: Ensure all output flows through the harness system for proper display
+
 ### Quality Standards
 
 - **Accuracy**: Ensure information is correct and up-to-date

data/templates/EXECUTE/00_PRD.md

@@ -4,10 +4,10 @@ You are a product strategist. Produce a **concise, complete PRD**.
 
 ## Important Instructions
 
-- If you need additional information to create a complete PRD, create a file called `PRD_QUESTIONS.md` with specific questions for the user.
-- If `PRD_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete PRD document.
-- Only ask for clarifications at this PRD step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete PRD, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete PRD document
+- Only ask for clarifications at this PRD step. For subsequent steps, proceed with available information
 
 ## Input
 

data/templates/EXECUTE/02_ARCHITECTURE.md

@@ -5,10 +5,11 @@ and **hexagonal structure**.
 
 ## Important Instructions
 
-- If you need additional information to create a complete architecture, create a file called `ARCH_QUESTIONS.md` with specific questions for the user (see `02A_ARCH_GATE_QUESTIONS.md` for suggested questions).
-- If `ARCH_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete architecture document.
-- Only ask for clarifications at this Architecture step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete architecture, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- See `02A_ARCH_GATE_QUESTIONS.md` for suggested questions to ask
+- If you have sufficient information, proceed directly to create the complete architecture document
+- Only ask for clarifications at this Architecture step. For subsequent steps, proceed with available information
 
 ## Inputs
 

data/templates/EXECUTE/07_TEST_PLAN.md

@@ -9,15 +9,18 @@ You are a test strategist.
 ## Process
 
 - Derive acceptance tests from user stories.
+- Give each test a clear and descriptive title, so that running tests in "documentation" format will create a clear specification of behavior.
 - Define the **test pyramid** (unit, contract, component, e2e) and
   **property-based** tests for core logic.
+- Avoid mocking non-external dependencies unless necessary.
 - Establish coverage & mutation-testing thresholds.
 - Follow Sandi Metz's rules for unit testing.
+- Tests should be written for maximum understandability, maintainability, and reviewability. Assume the reviewer is not familiar with the codebase.
 
 ## Output
 
 - `docs/TestPlan.md`
-- `golden/` fixtures directory plan
+- `spec/fixtures/` fixtures directory plan
 
 ## Regeneration Policy
 

data/templates/EXECUTE/08_TASKS.md

@@ -4,10 +4,10 @@ You are a planner.
 
 ## Important Instructions
 
-- If you need additional information to create a complete task plan, create a file called `TASKS_QUESTIONS.md` with specific questions for the user.
-- If `TASKS_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete task plan.
-- Only ask for clarifications at this Tasks step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete task plan, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete task plan
+- Only ask for clarifications at this Tasks step. For subsequent steps, proceed with available information
 
 ## Inputs
 

data/templates/EXECUTE/10_IMPLEMENTATION_AGENT.md

@@ -4,10 +4,10 @@ You are a senior engineer writing **implementation guidance** for domain agents.
 
 ## Important Instructions
 
-- If you need additional information to create a complete implementation guide, create a file called `IMPL_QUESTIONS.md` with specific questions for the user.
-- If `IMPL_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete implementation guide.
-- Only ask for clarifications at this Implementation step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete implementation guide, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete implementation guide
+- Only ask for clarifications at this Implementation step. For subsequent steps, proceed with available information
 
 ## Inputs
 

data/templates/README.md

@@ -0,0 +1,279 @@
+# AIDP Configuration Examples
+
+This directory contains example configuration files for the AIDP (AI Dev Pipeline) harness system. Choose the configuration that best fits your needs and copy it to your project root as `aidp.yml`.
+
+## Available Configuration Files
+
+### 1. `aidp.yml.example` - Complete Configuration
+
+**Best for**: Production use, comprehensive setups, advanced users
+
+This is the most comprehensive configuration file that demonstrates all available harness features including:
+
+- Complete harness configuration with all options
+- Multiple provider configurations (Cursor, Claude, Gemini)
+- Advanced features like circuit breakers, load balancing, health checks
+- Environment-specific configurations
+- Mode-specific configurations (analyze vs execute)
+- Feature flags
+- Time-based configurations
+- Step-specific configurations
+- User-specific configurations
+- Comprehensive monitoring and logging
+- Security configurations
+
+### 2. `aidp-minimal.yml.example` - Minimal Configuration
+
+**Best for**: Getting started, simple setups, basic usage
+
+This is a minimal configuration file that includes only the essential settings:
+
+- Basic harness configuration
+- Two providers (Cursor and Claude)
+- Essential features only
+- Simple retry and fallback configuration
+
+### 3. `aidp-production.yml.example` - Production Configuration
+
+**Best for**: Production deployments, enterprise use, high availability
+
+This configuration is optimized for production use with:
+
+- Comprehensive monitoring and alerting
+- Robust error handling and retry logic
+- Circuit breaker patterns for fault tolerance
+- Load balancing and health checks
+- Security configurations
+- Cost tracking and budgeting
+- Audit logging
+- Performance optimizations
+
+### 4. `aidp-development.yml.example` - Development Configuration
+
+**Best for**: Development, testing, debugging
+
+This configuration is optimized for development with:
+
+- Relaxed timeouts and retry settings
+- Enhanced logging and debugging
+- Disabled rate limiting for testing
+- Fast feedback loops
+- Detailed error reporting
+- Request/response logging
+
+## Quick Start
+
+1. **Choose a configuration file** based on your needs
+2. **Copy it to your project root** as `aidp.yml`:
+
+   ```bash
+   cp templates/aidp-minimal.yml.example aidp.yml
+   ```
+
+3. **Set up your API keys** in environment variables:
+
+   ```bash
+   export ANTHROPIC_API_KEY="your_api_key_here"
+   export GEMINI_API_KEY="your_api_key_here"
+   ```
+
+4. **Customize the configuration** for your specific needs
+5. **Run AIDP** with the harness:
+
+   ```bash
+   aidp analyze
+   aidp execute
+   ```
+
+## Configuration Sections
+
+### Harness Configuration
+
+The `harness` section controls the overall behavior of the harness system:
+
+- `default_provider`: Primary provider to use
+- `fallback_providers`: Backup providers in order of preference
+- `max_retries`: Number of retry attempts
+- `request_timeout`: Global request timeout
+- `auto_switch_on_error`: Automatically switch providers on errors
+- `auto_switch_on_rate_limit`: Automatically switch providers on rate limits
+
+### Provider Configuration
+
+The `providers` section defines individual provider settings:
+
+- `type`: Provider type (package, api, byok)
+- `priority`: Provider priority (higher = more preferred)
+- `models`: Available models for the provider
+- `features`: Provider capabilities
+- `auth`: Authentication configuration
+- `endpoints`: API endpoints
+- `monitoring`: Monitoring and metrics
+- `rate_limit`: Rate limiting settings
+- `retry`: Retry configuration
+- `circuit_breaker`: Circuit breaker settings
+- `cost`: Cost tracking
+- `health_check`: Health check configuration
+- `log`: Logging configuration
+- `cache`: Caching configuration
+- `security`: Security settings
+
+### Advanced Features
+
+#### Environment-Specific Configuration
+
+Use the `environments` section to have different settings for different environments:
+
+```yaml
+environments:
+  development:
+    harness:
+      max_retries: 1
+  production:
+    harness:
+      max_retries: 3
+```
+
+#### Mode-Specific Configuration
+
+Use the `analyze_mode` and `execute_mode` sections for different execution modes:
+
+```yaml
+analyze_mode:
+  harness:
+    request_timeout: 600
+execute_mode:
+  harness:
+    request_timeout: 300
+```
+
+#### Feature Flags
+
+Use the `features` section to enable/disable functionality:
+
+```yaml
+features:
+  debugging:
+    harness:
+      log_errors: true
+```
+
+#### Time-Based Configuration
+
+Use the `time_based` section for different settings based on time:
+
+```yaml
+time_based:
+  hours:
+    9..17:  # Business hours
+      harness:
+        max_retries: 2
+```
+
+## Provider Types
+
+### Package Providers
+
+- **Type**: `package`
+- **Pricing**: Fixed monthly/yearly subscription
+- **Examples**: Cursor Pro
+- **Configuration**: No API keys needed
+
+### API Providers
+
+- **Type**: `api`
+- **Pricing**: Pay-per-use based on tokens
+- **Examples**: Claude, Gemini
+- **Configuration**: Requires API keys
+
+### BYOK Providers
+
+- **Type**: `byok`
+- **Pricing**: User provides their own API key
+- **Examples**: OpenAI, custom APIs
+- **Configuration**: User manages API keys
+
+## Best Practices
+
+### Security
+
+- Store API keys in environment variables, not in the config file
+- Use `restrict_to_non_byok: true` to avoid BYOK providers
+- Enable SSL verification in production
+- Configure allowed/blocked hosts appropriately
+
+### Performance
+
+- Enable caching for frequently used responses
+- Use appropriate timeouts for different models
+- Configure rate limits based on your API plans
+- Enable parallel processing for better throughput
+
+### Reliability
+
+- Configure fallback providers for automatic failover
+- Enable circuit breakers for fault tolerance
+- Set up health checks for all providers
+- Configure appropriate retry strategies
+
+### Monitoring
+
+- Enable metrics collection in production
+- Set up log rotation and retention
+- Configure monitoring intervals appropriately
+- Enable audit logging for compliance
+
+### Cost Management
+
+- Configure cost tracking for API providers
+- Set appropriate token limits
+- Monitor usage and costs regularly
+- Use cost-effective models when possible
+
+## Troubleshooting
+
+### Common Issues
+
+1. **Provider not working**: Check API keys and endpoints
+2. **Rate limiting**: Adjust rate limit settings or use fallback providers
+3. **Timeout errors**: Increase timeout values
+4. **Configuration errors**: Validate your YAML syntax
+5. **Permission errors**: Check file permissions for log files
+
+### Validation
+
+Use the AIDP configuration validator to check your configuration:
+
+```bash
+aidp config validate
+```
+
+### Debugging
+
+Enable debug logging to troubleshoot issues:
+
+```yaml
+providers:
+  your_provider:
+    log:
+      level: "debug"
+      log_requests: true
+      log_responses: true
+```
+
+## Support
+
+For more information about AIDP configuration, see:
+
+- [AIDP Documentation](https://github.com/your-org/aidp/docs)
+- [Configuration Schema](https://github.com/your-org/aidp/docs/configuration-schema.md)
+- [Provider Guide](https://github.com/your-org/aidp/docs/providers.md)
+
+## Contributing
+
+To contribute new configuration examples or improve existing ones:
+
+1. Fork the repository
+2. Create a new configuration file or modify an existing one
+3. Test your configuration thoroughly
+4. Submit a pull request with your changes